Skip to main content

Full text of "TS 125 413 - V4.10.0 - Universal Mobile Telecommunications System (UMTS); UTRAN Iu interface Radio Access Network Application Part (RANAP) signalling (3GPP TS 25.413 version 4.10.0 Release 4)"

See other formats


ETSITS125 413V4.10.0 



(2003-09) 



Technical Specification 



Universal Mobile Telecommunications System (UMTS); 

UTRAN lu interface Radio Access Network 

Application Part (RANAP) signalling 

(3GPP TS 25.413 version 4.10.0 Release 4) 



3ji^ 




3GPP TS 25.41 3 version 4.1 0.0 Release 4 1 ETSI TS 1 25 41 3 V4.1 0.0 (2003-09) 



Reference 



RTS/TSGR-032541 3v4a0 
Keywords 



UMTS 



ETSI 

650 Route des Lucioles 
F-06921 Sophia Antipolis Cedex - FRANCE 

Tel. : +33 4 92 94 42 00 Fax: +33 4 93 65 47 1 6 

Siret N ° 348 623 562 0001 7 - NAF 742 C 
Association a but non lucratif enregistree a la 
Sous-Prefecture de Grasse (06) N° 7803/88 



Important notice 



Individual copies of the present document can be downloaded from: 
http://www.etsi.orq 

The present document may be made available in more than one electronic version or in print. In any case of existing or 

perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF). 

In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive 

within ETSI Secretariat. 

Users of the present document should be aware that the document may be subject to revision or change of status. 

Information on the current status of this and other ETSI documents is available at 

http://portal.etsi.orq/tb/status/status.asp 

If you find errors in the present document, send your comment to: 
editor(a)etsi.orq 

Copyright Notification 

No part may be reproduced except as authorized by written permission. 
The copyright and the foregoing restriction extend to reproduction in all media. 

© European Telecommunications Standards Institute 2003. 
All rights reserved. 

DECT'^", PLUGTESTS™ and UMTS™ are Trade IVlarks of ETSI registered for the benefit of its IVIembers. 
TIPHON^" and the TIPHON logo are Trade Marks currently being registered by ETSI for the benefit of its Members. 
2QppTM |g g jracle Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. 



ETSI 



3GPP TS 25.41 3 version 4.1 0.0 Release 4 2 ETSI TS 1 25 41 3 V4.1 0.0 (2003-09) 



Intellectual Property Rights 



IPRs essential or potentially essential to the present document may have been declared to ETSI. The information 
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found 
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in 
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web 
server ( http://webapp.etsi.org/IPR/home.asp ). 

Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee 
can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web 
server) which are, or may be, or may become, essential to the present document. 



Foreword 

This Technical Specification (TS) has been produced by ETSI 3rd Generation Partnership Project (3GPP). 

The present document may refer to technical specifications or reports using their 3GPP identities, UMTS identities or 
GSM identities. These should be interpreted as being references to the corresponding ETSI deliverables. 

The cross reference between GSM, UMTS, 3GPP and ETSI identities can be found under 
http://webapp.etsi.org/kev/quervform.asp . 



ETSI 



3GPP TS 25.41 3 version 4.1 0.0 Release 4 3 ETSI TS 1 25 41 3 V4.1 0.0 (2003-09) 



Contents 



Intellectual Property Rights 2 

Foreword 2 

Foreword 9 

1 Scope 10 

2 References 10 

3 Definitions, symbols and abbreviations 11 

3.1 Definitions 11 

3.2 Symbols 12 

3.3 Abbreviations 12 

4 General 13 

4.1 Procedure Specification Principles 13 

4.2 Forwards and Backwards Compatibility 14 

4.3 Specification Notations 14 

5 RANAP Services 14 

6 Services Expected from Signalling Transport 14 

7 Functions of RANAP 15 

8 RANAP Procedures 16 

8.1 Elementary Procedures 16 

8.2 RAB Assignment 17 

8.2.1 General 17 

8.2.2 Successful Operation 18 

8.2.3 Unsuccessful Operation 23 

8.2.4 Abnormal Conditions 23 

8.3 RAB Release Request 24 

8.3.1 General 24 

8.3.2 Successful Operation 24 

8.3.3 Abnormal Conditions 24 

8.4 lu Release Request 24 

8.4.1 General 24 

8.4.2 Successful Operation 25 

8.4.3 Abnormal Conditions 25 

8.5 lu Release 25 

8.5.1 General 25 

8.5.2 Successful Operation 25 

8.5.3 Abnormal Conditions 26 

8.6 Relocation Preparation 26 

8.6.1 General 26 

8.6.2 Successful Operation 27 

8.6.3 Unsuccessful Operation 29 

8.6.4 Abnormal Conditions 29 

8.6.5 Co-ordination of Two lu Signalling Connections 30 

8.7 Relocation Resource Allocation 30 

8.7.1 General 30 

8.7.2 Successful Operation 30 

8.7.3 Unsuccessful Operation 33 

8.7.4 Abnormal Conditions 34 

8.7.5 Co-ordination of Two lu Signalling Connections 34 

8.8 Relocation Detect 35 

8.8.1 General 35 

8.8.2 Successful Operation 35 

8.8.3 Abnormal Conditions 35 



£75/ 



3GPP TS 25.41 3 version 4.1 0.0 Release 4 4 ETSI TS 1 25 41 3 V4.1 0.0 (2003-09) 

8.8.4 Co-ordination of Two lu Signalling Connections 35 

8.9 Relocation Complete 35 

8.9.1 General 35 

8.9.2 Successful Operation 36 

8.9.3 Abnormal Conditions 36 

8.9.4 Co-ordination of Two lu Signalling Connections 36 

8.10 Relocation Cancel 36 

8.10.1 General 36 

8.10.2 Successful Operation 37 

8.10.3 Unsuccessful Operation 37 

8.10.4 Abnormal Conditions 37 

8.10.5 Co-ordination of Two lu Signalling Connections 37 

8.11 SRNS Context Transfer 37 

8.11.1 General 37 

8.11.2 Successful Operation 38 

8.11.3 Unsuccessful Operation 38 

8.11.4 Abnormal Conditions 38 

8.12 SRNS Data Forwarding Initiation 38 

8.12.1 General 38 

8.12.2 Successful Operation 39 

8.12.3 Abnormal Conditions 39 

8.13 SRNS Context Forwarding from Source RNC to CN 39 

8.13.1 General 39 

8.13.2 Successful Operation 39 

8.13.3 Abnormal Conditions 40 

8.14 SRNS Context Forwarding to Target RNC from CN 40 

8.14.1 General 40 

8.14.2 Successful Operation 40 

8.14.3 Abnormal Conditions 40 

8.15 Paging 41 

8.15.1 General 41 

8.15.2 Successful Operation 41 

8.15.3 Abnormal Conditions 42 

8.16 Common ID 42 

8.16.1 General 42 

8.16.2 Successful Operation 42 

8.16.3 Abnormal Conditions 42 

8.17 CN Invoke Trace 42 

8.17.1 General 42 

8.17.2 Successful Operation 42 

8.17.3 Abnormal Conditions 43 

8.18 Security Mode Control 43 

8.18.1 General 43 

8.18.2 Successful Operation 43 

8.18.3 Unsuccessful Operation 44 

8.18.4 Abnormal Conditions 45 

8.19 Location Reporting Control 45 

8.19.1 General 45 

8.19.2 Successful Operation 45 

8.19.3 Abnormal Conditions 46 

8.20 Location Report 46 

8.20.1 General 46 

8.20.2 Successful Operation 46 

8.20.3 Abnormal Conditions 47 

8.21 Data Volume Report 47 

8.21.1 General 47 

8.21.2 Successful Operation 48 

8.21.3 Unsuccessful Operation 48 

8.21.4 Abnormal Conditions 48 

8.22 Initial UE Message 48 

8.22.1 General 48 

8.22.2 Successful Operation 49 



£75/ 



3GPP TS 25.41 3 version 4.1 0.0 Release 4 5 ETSI TS 1 25 41 3 V4.1 0.0 (2003-09) 

8.23 Direct Transfer 49 

8.23.1 General 49 

8.23.2 Successful Operation 50 

8.23.2.1 CN Originated Direct Transfer 50 

8.23.2.2 UTRAN Originated Direct Transfer 50 

8.23.3 Abnormal Conditions 50 

8.24 Void 50 

8.25 Overload Control 51 

8.25.1 General 51 

8.25.2 Philosophy 51 

8.25.3 Successful Operation 52 

8.25.3.1 Overload at the CN 52 

8.25.3.2 Overload at the UTRAN 52 

8.25.4 Abnormal Conditions 52 

8.26 Reset 52 

8.26.1 General 52 

8.26.2 Successful Operation 53 

8.26.2.1 Reset Procedure Initiated from the CN 53 

8.26.2.2 Reset Procedure Initiated from the UTRAN 53 

8.26.3 Abnormal Conditions 54 

8.26.3.1 Abnormal Condition at the CN 54 

8.26.3.2 Abnormal Condition at the UTRAN 54 

8.26.3.3 Crossing of Reset Messages 54 

8.27 Error Indication 54 

8.27.1 General 54 

8.27.2 Successful Operation 54 

8.27.3 Abnormal Conditions 55 

8.28 CN Deactivate Trace 55 

8.28.1 General 55 

8.28.2 Successful Operation 55 

8.28.3 Abnormal Conditions 56 

8.29 Reset Resource 56 

8.29.1 General 56 

8.29.1.1 Reset Resource procedure initiated from the RNC 56 

8.29.1.2 Reset Resource procedure initiated from the CN 56 

8.29.2 Successful Operation 56 

8.29.2.1 Reset Resource procedure initiated from the RNC 56 

8.29.2.2 Reset Resource procedure initiated from the CN 57 

8.30 RAB Modification Request 57 

8.30.1 General 57 

8.30.2 Successful Operation 57 

8.30.3 Abnormal Conditions 58 

8.31 Location Related Data 58 

8.31.1 General 58 

8.31.2 Successful Operation 58 

8.31.3 Unsuccessful Operation 59 

8.31.4 Abnormal Conditions 59 

9 Elements for RANAP Communication 59 

9.1 Message Functional Definition and Content 59 

9.1.1 General 59 

9.1.2 Message Contents 60 

9.1.2.1 Presence 60 

9.1.2.2 Criticality 60 

9.1.2.3 Range 60 

9.1.2.4 Assigned Criticality 60 

9.1.3 RAB ASSIGNMENT REQUEST 60 

9.1.4 RAB ASSIGNMENT RESPONSE 62 

9.1.5 RAB RELEASE REQUEST 64 

9.1.6 lU RELEASE REQUEST 64 

9.1.7 lU RELEASE COMMAND 64 

9.1.8 lU RELEASE COMPLETE 65 



£75/ 



3GPP TS 25.41 3 version 4.1 0.0 Release 4 6 ETSI TS 1 25 41 3 V4.1 0.0 (2003-09) 

9.1.9 RELOCATION REQUIRED 65 

9.1.10 RELOCATION REQUEST 66 

9.1.11 RELOCATION REQUEST ACKNOWLEDGE 68 

9.1.12 RELOCATION COMMAND 68 

9.1.13 RELOCATION DETECT 69 

9.1.14 RELOCATION COMPLETE 69 

9.1.15 RELOCATION PREPARATION FAILURE 70 

9.1.16 RELOCATION FAILURE 70 

9.1.17 RELOCATION CANCEL 70 

9.1.18 RELOCATION CANCEL ACKNOWLEDGE 70 

9.1. 19 SRNS CONTEXT REQUEST 70 

9.1.20 SRNS CONTEXT RESPONSE 71 

9.1.21 SRNS DATA FORWARD COMMAND 71 

9.1.22 FORWARD SRNS CONTEXT 72 

9.1.23 PAGING 72 

9.1.24 COMMON ID 73 

9.1.25 CN INVOKE TRACE 73 

9.1.26 SECURITY MODE COMMAND 73 

9.1.27 SECURITY MODE COMPLETE 74 

9.1.28 SECURITY MODE REJECT 74 

9.1.29 LOCATION REPORTING CONTROL 74 

9.1.30 LOCATION REPORT 75 

9.1.31 DATA VOLUME REPORT REQUEST 75 

9.1.32 DATA VOLUME REPORT 75 

9.1.33 INITIAL UE MESSAGE 76 

9.1.34 DIRECT TRANSFER 76 

9.1.35 CN INFORMATION BROADCAST REQUEST 77 

9.1.36 CN INFORMATION BROADCAST CONFIRM 77 

9.1.37 CN INFORMATION BROADCAST REJECT 77 

9.1.38 OVERLOAD 77 

9.1.39 RESET 77 

9.1.40 RESET ACKNOWLEDGE 77 

9.1.41 ERROR INDICATION 78 

9.1.42 CN DEACTIVATE TRACE 78 

9.1.43 RANAP RELOCATION INFORMATION 78 

9.1.44 RESET RESOURCE 79 

9.1.45 RESET RESOURCE ACKNOWLEDGE 81 

9.1.46 RAB MODIFY REQUEST 81 

9.1.47 LOCATION RELATED DATA REQUEST 82 

9.1.48 LOCATION RELATED DATA RESPONSE 82 

9.1.49 LOCATION RELATED DATA FAILURE 82 

9.2 Information Element Definitions 83 

9.2.0 General 83 

9.2.1 Radio Network Layer Related lEs 83 

9.2.1.1 Message Type 83 

9.2.1.2 RABID 84 

9.2.1.3 RAB Parameters 85 

9.2.1.4 Cause 90 

9.2.1.5 CN Domain Indicator 97 

9.2.1.6 Trace Type 97 

9.2.1.7 Trigger ID 97 

9.2.1.8 Trace Reference 97 

9.2.1.9 UE Identity 98 

9.2.1.10 OMCID 98 

9.2.1.11 Integrity Protection Information 98 

9.2.1.12 Encryption Information 99 

9.2.1.13 Chosen Integrity Protection Algorithm 99 

9.2.1.14 Chosen Encryption Algorithm 99 

9.2.1.15 Categorisation Parameters 99 

9.2.1. 16 Request Type 99 

9.2.1.17 Data Volume Reporting Indication 100 

9.2.1.18 User Plane Mode 100 



£75/ 



3GPP TS 25.41 3 version 4.1 0.0 Release 4 7 ETSI TS 1 25 41 3 V4.1 0.0 (2003-09) 

9.2.1.19 UP Mode Versions 100 

9.2.1.20 Chosen UP Version 101 

9.2.1.21 Paging Area ID 101 

9.2.1.22 Non Searching Indication 101 

9.2.1.23 Relocation Type 101 

9.2.1.24 Source ID 101 

9.2.1.25 Target ID 102 

9.2.1.26 MSClassmark2 102 

9.2.1.27 MSClassmark3 102 

9.2.1.28 Source RNC to Target RNC Transparent Container 103 

9.2.1.29 Old BSS to New BSS Information 106 

9.2.1.30 Target RNC to Source RNC Transparent Container 106 

9.2.1.31 L3 Information 106 

9.2.1.32 Number of Steps 106 

9.2.1.33 DL N-PDU Sequence Number 107 

9.2.1.34 UL N-PDU Sequence Number 107 

9.2.1.35 Criticality Diagnostics 107 

9.2.1.36 Key Status 109 

9.2.1.37 DRX Cycle Length Coefficient 109 

9.2.1.38 lu Signalling Connection Identifier 109 

9.2.1.39 Global RNC-ID 109 

9.2.1.40 PDP Type Information 110 

9.2.1.41 Service Handover 110 

9.2.1.42 Message Structure Ill 

9.2.1.43 Alternative RAB Parameter Values 112 

9.2.1.44 Assigned RAB Parameter Values 113 

9.2.1.45 Requested RAB Parameter Values 113 

9.2.1.46 Global CN-ID 114 

9.2.1.46a Vertical Accuracy Code 114 

9.2.1.46b Response Time 115 

9.2.1.46c Positioning Priority 115 

9.2.1.46d Client Type 115 

9.2.2 Transport Network Layer Related IBs 115 

9.2.2.1 Transport Layer Address 115 

9.2.2.2 lu Transport Association 116 

9.2.2.3 DL GTP-PDU Sequence Number 116 

9.2.2.4 UL GTP-PDU Sequence Number 116 

9.2.3 NAS Related IBs 116 

9.2.3.1 Permanent NAS UB Identity 116 

9.2.3.2 Temporary UB ID 117 

9.2.3.3 Paging Cause 117 

9.2.3.4 NAS Broadcast Information 118 

9.2.3.5 NASPDU 118 

9.2.3.6 LAI 118 

9.2.3.7 RAC 119 

9.2.3.8 SAPI 119 

9.2.3.9 SAI 119 

9.2.3.10 Area Identity 120 

9.2.3.11 Geographical Area 120 

9.2.3.12 Unsuccessfully Transmitted Data Volume 123 

9.2.3.13 Data Volume Reference 123 

9.2.3.14 Information Identity 123 

9.2.3.15 Information Priority 123 

9.2.3.16 Information Control 124 

9.2.3.17 CN Broadcast Area 124 

9.2.3.18 NAS Synchronisation Indicator 124 

9.2.3.19 Location Related Data Request Type 124 

9.2.3.20 Broadcast Assistance Data Deciphering keys 124 

9.2.3.21 Requested GPS Assistance Data 125 

9.2.3.22 Last Known Service Area 125 

9.3 Message and Information Blement Abstract Syntax (with ASN.l) 126 

9.3.0 General 126 



£75/ 



3GPP TS 25.41 3 version 4.1 0.0 Release 4 8 ETSI TS 1 25 41 3 V4.1 0.0 (2003-09) 

9.3.1 Usage of private message mechanism for non-standard use 126 

9.3.2 Elementary Procedure Definitions 126 

9.3.3 PDU Definitions 134 

9.3.4 Information Element Definitions 170 

9.3.5 Common Definitions 191 

9.3.6 Constant Definitions 192 

9.3.7 Container Definitions 195 

9.4 Message Transfer Syntax 200 

9.5 Timers 200 

10 Handling of Unknown, Unforeseen and Erroneous Protocol Data 201 

10.1 General 201 

10.2 Transfer Syntax Error 201 

10.3 Abstract Syntax Error 202 

10.3.1 General 202 

10.3.2 Criticality Information 202 

10.3.3 Presence Information 203 

10.3.4 Not comprehended lE/lE group 203 

10.3.4.1 Procedure Code 203 

10.3.4.1A Type of Message 203 

10.3.4.2 lEs other than the Procedure Code and Type of Message 203 

10.3.5 Missing IE or IE group 205 

10.3.6 lEs or IE groups received in wrong order or with too many occurrences or erroneously present 206 

10.4 Logical Error 206 

10.5 Exceptions 207 

11 Special Procedures for RNC to RNC Communication 207 

11.1 General 207 

11.2 RANAP Relocation Information 207 

11.2.1 General 207 

11.2.2 Operation 207 

Annex A (informative): RANAP guidelines 209 

A.l Rules for building RANAP messages 209 

A. 1.1 Rules for RANAP messages that shall contain the CN Domain Indicator IE 209 

A.2 Guidelines for Usage of the Criticality Diagnostics IE 209 

A.2.1 EXAMPLE MESSAGE Layout 209 

A.2.2 Example on a Received EXAMPLE MESSAGE 210 

A.2. 3 Content of Criticality Diagnostics 211 

A.2.3.1 Example 1 211 

A. 2. 3. 2 Example 2 212 

A.2.3.3 Example 3 213 

A.2.3.4 Example 4 214 

A.2.3.5 Example 5 215 

A.2.4 ASN.l of EXAMPLE MESSAGE 216 

Annex B (informative): Change history 219 

History 222 



£75/ 



3GPP TS 25.41 3 version 4.1 0.0 Release 4 9 ETSI TS 1 25 41 3 V4.1 0.0 (2003-09) 



Foreword 



rd , 



This Technical Specification (TS) has been produced by the 3 Generation Partnership Project (3GPP). 

The contents of the present document are subject to continuing work within the TSG and may change following formal 
TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an 
identifying change of release date and an increase in version number as follows: 

Version x.y.z 

where: 

X the first digit: 

1 presented to TSG for information; 

2 presented to TSG for approval; 

3 or greater indicates TSG approved document under change control. 

y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, 
updates, etc. 

z the third digit is incremented when editorial only changes have been incorporated in the document. 



£75/ 



3GPP TS 25.41 3 version 4.1 0.0 Release 4 1 ETSI TS 1 25 41 3 V4.1 0.0 (2003-09) 



Scope 



The present document specifies the radio network layer signalling protocol called Radio Access Network Application 
Part (RANAP) for the lu interface. RANAP supports the functions of lu interface by signalling procedures defined in 
this document. RANAP is developed in accordance to the general principles stated in [1], [2] and [3]. 



References 



The following documents contain provisions which, through reference in this text, constitute provisions of the present 
document. 

• References are either specific (identified by date of publication, edition number, version number, etc.) or 
non-specific. 

• For a specific reference, subsequent revisions do not apply". 

• For a non-specific reference, the latest version applies". 

[I] 3GPP TR 23.930: "lu Principles". 

[2] 3GPP TS 25.410: "UTRAN lu Interface: General Aspects and Principles". 

[3] 3GPP TS 25.401: "UTRAN Overall Description". 

[4] 3GPP TR 25.931: "UTRAN Functions, Examples on Signalling Procedures". 

[5] 3GPP TS 25.412: "UTRAN lu interface signalling transport". 

[6] 3GPP TS 25.415: "UTRAN lu interface user plane protocols". 

[7] 3GPP TS 23.107: "Quality of Service (QoS) concept and architecture". 

[8] 3GPP TS 24.008: "Mobile radio interface layer 3 specification; Core network protocols; Stage 3". 

[9] 3GPP TS 25.414: "UTRAN lu interface data transport and transport signalling". 

[10] 3GPP TS 25.331: Radio Ressource Control (RRC) protocol specification". 

[II] 3GPP TS 08.08: "Mobile services Switching Centre - Base Station System (MSC-BSS) interface; 
Layer 3 specification". 

[12] 3GPP TS 12.08: "Subscriber and equipment trace". 

[13] ITU-T Recommendation X.691 (1997): "Information technology - ASN.l encoding rules: 

Specification of Packed Encoding Rules (PER)". 

[14] ITU-T Recommendation X.680 (1997): "Information technology - Abstract Syntax Notation One 

(ASN.l): Specification of basic notation". 

[15] ITU-T Recommendation X.681 (1997): "Information technology - Abstract Syntax Notation One 

(ASN.l): Information object specification". 

[16] 3GPP TS 23.1 10: "UMTS Access Stratum, Services and Functions". 

[17] 3GPP TS 25.323: "Packet Data Convergence Protocol (PDCP) specification". 

[18] 3GPP TR 25.921: "Guidelines and principles for protocol description and error handling". 

[19] 3GPP TS 23.003: "Numbering, addressing and identification". 

[20] 3GPP TS 23.032: "Universal Geographical Area Description (GAD)". 

[21] 3GPP TS 23.060: "General Packet Radio Service (GPRS); Service description; Stage 2". 



£75/ 



3GPP TS 25.41 3 version 4.1 0.0 Release 4 1 1 ETSI TS 1 25 41 3 V4.1 0.0 (2003-09) 

[22] 3GPP TS 24.080: "Mobile radio Layer 3 supplementary services specification; Formats and 

coding". 

[23] 3GPP TS 29. 108: "Application of the Radio Access Network Application Part (RANAP) on the 

E-interface". 

[24] 3GPP TS 29.002: "Mobile Apphcation Part (MAP) specification". 

[25] 3GPP TS 12.20: "Base Station System (BSS) management information". 

[26] 3GPP TS 22.071: "Location Services (LCS); Service description - Stage 1". 

3 Definitions, symbols and abbreviations 

3.1 Definitions 

For the purposes of the present document, the following terms and definitions apply. 

Integrity Protection Alternative: defines both the Integrity Protection Status (started/not started) together with the 
Integrity Protection Algorithm considered altogether. 

Ciphering Alternative: defines both the Ciphering Status (started/not started) together with the Ciphering Algorithm 
considered altogether. 

Default CN node: An RNC has one single permanent default CN node per CN domain. It always initiates the Initial UE 
Message procedure towards its default CN node. 

Relocation of SRNS: relocation of SRNS is a UMTS functionality used to relocate the serving RNS role from one RNS 
to another RNS. This UMTS functionality is realised by several elementary procedures executed in several interfaces 
and by several protocols and it may involve a change in the radio resources used between UTRAN and UE 

It is also possible to relocate the serving RNS role from: 

one RNS within UMTS to another relocation target external to UMTS; 

functionality equivalent to the serving RNS role from another relocation source external to UMTS to another 
RNS. 

Serving RNS (SRNS): role an RNS can take with respect to a specific connection between an UE and UTRAN. There 
is one serving RNS for each UE that has a connection to UTRAN. The serving RNS is in charge of the radio connection 
between a UE and the UTRAN. The serving RNS terminates the lu for this UE 

Serving RNC (SRNC): SRNC is the RNC belonging to SRNS 

SRNC-ID: see [3] for definition 

S-RNTI: see [3] for definition 

Source RNS: role, with respect to a specific connection between UTRAN and CN, that RNS takes when it decides to 
initiate a relocation of SRNS 

Source RNC: source RNC is the RNC belonging to source RNS 

Target RNS: role an RNS gets with respect to a specific connection between UTRAN and CN when it is being a 
subject of a relocation of SRNS which is being made towards that RNS 

Target RNC: target RNC is the RNC belonging to target RNS 

Directed retry: Directed retry is the process of assigning a User Equipment to a radio resource that does not belong to 
the serving RNC e.g. in situations of congestion. It is triggered by the RAB Assignment procedure and employs 
relocation procedures. 



£75/ 



3GPP TS 25.41 3 version 4.1 0.0 Release 4 1 2 ETSI TS 1 25 41 3 V4.1 0.0 (2003-09) 

Elementary Procedure: RANAP protocol consists of Elementary Procedures (EPs). An Elementary Procedure is a unit 
of interaction between the RNS and the CN. These Elementary Procedures are defined separately and are intended to be 
used to build up complete sequences in a flexible manner. If the independence between some EPs is restricted, it is 
described under the relevant EP description. Unless otherwise stated by the restrictions, the EPs may be invoked 
independently of each other as stand alone procedures, which can be active in parallel. Examples on using several 
RANAP EPs together with each other and EPs from other interfaces can be found in reference [4]. 

An EP consists of an initiating message and possibly a response message. Three kinds of EPs are used: 

Class 1: Elementary Procedures with response (success and/or failure). 

Class 2: Elementary Procedures without response. 

Class 3: Elementary Procedures with possibility of multiple responses. 

For Class 1 EPs, the types of responses can be as follows: 

Successful: 

A signalling message explicitly indicates that the elementary procedure successfully completed with the 
receipt of the response. 

Unsuccessful: 

A signalling message explicitly indicates that the EP failed. 

On time supervision expiry (i.e. absence of expected response). 

Successful and Unsuccessful: 

One signalling message reports both successful and unsuccessful outcome for the different included requests. 
The response message used is the one defined for successful outcome. 

Class 2 EPs are considered always successful. 

Class 3 EPs have one or several response messages reporting both successful, unsuccessful outcome of the requests and 
temporary status information about the requests. This type of EP only terminates through response(s) or EP timer 
expiry. 

3.2 Symbols 

Void. 

3.3 Abbreviations 

For the purposes of the present document, the following abbreviations apply: 

AAL2 ATM Adaptation Layer type 2 

AS Access Stratum 

ASN. 1 Abstract Syntax Notation One 

ATM Asynchronous Transfer Mode 

CC Call Control 

CN Core Network 

CRNC Controlling RNC 

CS Circuit Switched 

DCH Dedicated Channel 

DL Downlink 

DRNC Drift RNC 

DRNS Drift RNS 

DSCH Downlink Shared Channel 

EP Elementary Procedure 

GPRS General Packet Radio System 

GSM Global System for Mobile communications 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



13 



ETSI TS 125 413 V4.10.0 (2003-09) 



GTP GPRS Tunnelling Protocol 

IE Information Element 

IMEI International Mobile Equipment Identity 

IMSI International Mobile Subscriber Identity 

IPv4 Internet Protocol (version 4) 

IPv6 Internet Protocol (version 6) 

MM Mobility Management 

MSC Mobile services Switching Center 

NAS Non Access Stratum 

N-PDU Network - Protocol Data Unit 

OSP:IHOSS Octet Stream Protocol: Internet-Hosted Octet Stream Service 

P-TMSI Packet TMSI 

PDCP Packet Data Convergence Protocol 

PDP Packet Data Protocol 

PDU Protocol Data Unit 

PPP Point-to-Point Protocol 

PS Packet Switched 

QoS Quality of Service 

RAB Radio Access Bearer 

RANAP Radio Access Network Application Part 

RNC Radio Network Controller 

RNS Radio Network Subsystem 

RRC Radio Resource Control 

SAI Service Area Identifier 

SAP Service Access Point 

SCCP Signalling Connection Control Part 

SDU Service Data Unit 

SGSN Serving GPRS Support Node 

SRNC Serving RNC 

SRNS Serving RNS 

TEID Tunnel Endpoint Identifier 

TMSI Temporary Mobile Subscriber Identity 

UE User Equipment 

UEA UMTS Encryption Algorithm 

UIA UMTS Integrity Algorithm 

UL UpUnk 

UMTS Universal Mobile Telecommunications System 

USCH Uplink Shared Channel 

UTRAN UMTS Terrestrial Radio Access Network 



4 General 

4.1 Procedure Specification Principles 

The principle for specifying the procedure logic is to specify the functional behaviour of the RNC exactly and 
completely. The CN functional behaviour is left unspecified. The EPs Relocation Preparation, Reset, Reset Resource 
and Overload Control are exceptions from this principle. 

The following specification principles have been applied for the procedure text in clause 8: 

The procedure text discriminates between: 

1) Functionality which "shall" be executed 

The procedure text indicates that the receiving node "shall" perform a certain function Y under a certain 
condition. If the receiving node supports procedure X but cannot perform functionality Y requested in the 
REQUEST message of a Class 1 of Class 3 EP, the receiving node shall respond with the message used to 
report unsuccessful outcome for this procedure, containing an appropriate cause value. 

2) Functionality which "shall, if supported" be executed 



£75/ 



3GPP TS 25.41 3 version 4.1 0.0 Release 4 1 4 ETSI TS 1 25 41 3 V4.1 0.0 (2003-09) 

The procedure text indicates that the receiving node "shall, if supported," perform a certain function Y under 
a certain condition. If the receiving node supports procedure X, but does not support functionality Y, the 
receiving node shall proceed with the execution of the EP, possibly informing the requesting node about the 
not supported functionality. 

Any required inclusion of an optional IE in a response message is explicitly indicated in the procedure text. If the 
procedure text does not explicitly indicate that an optional IE shall be included in a response message, the 
optional IE shall not be included. 

4.2 Forwards and Backwards Compatibility 

The forwards and backwards compatibility of the protocol is assured by mechanism where all current and future 
messages, and lEs or groups of related lEs, include ID and criticality fields that are coded in a standard format that will 
not be changed in the future. These parts can always be decoded regardless of the standard version. 

4.3 Specification Notations 

For the purposes of the present document, the following notations apply: 

Procedure When referring to an elementary procedure in the specification the Procedure Name is written with 

the first letters in each word in upper case characters followed by the word "procedure", e.g. RAB 
Assignment procedure. 

Message When referring to a message in the specification the MESSAGE NAME is written with all letters 

in upper case characters followed by the word "message", e.g. RAB ASSIGNMENT REQUEST 
message. 

IE When referring to an information element (IE) in the specification the Information Element Name 

is written with the first letters in each word in upper case characters and all letters in Italic font 
followed by the abbreviation "IE", e.g. User Plane Mode IE. 

Value of an IE When referring to the value of an information element (IE) in the specification the "Value" is 

written as it is specified in subclause 9.2 enclosed by quotation marks, e.g. "Abstract Syntax Error 
(Reject)" or "Geographical Coordinates". 



RANAP Services 



RANAP provides the signalling service between UTRAN and CN that is required to fulfil the RANAP functions 
described in clause 7. RANAP services are divided into three groups based on Service Access Points (SAP) defined in 
[16]: 

1. General control services: They are related to the whole lu interface instance between RNC and logical CN 
domain, and are accessed in CN through the General Control SAP. They utilise connectionless signalling 
transport provided by the lu signalling bearer. 

2. Notification services: They are related to specified UEs or all UEs in specified area, and are accessed in CN 
through the Notification SAP. They utilise connectionless signalling transport provided by the lu signalling 
bearer. 

3. Dedicated control services: They are related to one UE, and are accessed in CN through the Dedicated Control 
SAP. RANAP functions that provide these services are associated with lu signalling connection that is 
maintained for the UE in question. The lu signalling connection is realised with connection oriented signalling 
transport provided by the lu signalling bearer. 



6 Services Expected from Signalling Transport 

Signalling transport (See [5]) shall provide two different service modes for the RANAP. 



£75/ 



3GPP TS 25.41 3 version 4.1 0.0 Release 4 1 5 ETSI TS 1 25 41 3 V4.1 0.0 (2003-09) 

1 . Connection oriented data transfer service. This service is supported by a signalling connection between RNC and 
CN domain. It shall be possible to dynamically establish and release signalling connections based on the need. 
Each active UE shall have its own signalling connection. The signalling connection shall provide in sequence 
delivery of RANAP messages. RANAP shall be notified if the signalling connection breaks. 

2. Connectionless data transfer service. RANAP shall be notified in case a RANAP message did not reach the 
intended peer RANAP entity. 



7 Functions of RANAP 

RANAP protocol has the following functions: 

Relocating serving RNC. This function enables to change the serving RNC functionality as well as the related lu 
resources (RAB(s) and Signalling connection) from one RNC to another. 

Overall RAB management. This function is responsible for setting up, modifying and releasing RABs. 

Queuing the setup of RAB. The purpose of this function is to allow placing some requested RABs into a queue, 
and indicate the peer entity about the queuing. 

Requesting RAB release. While the overall RAB management is a function of the CN, the RNC has the 
capability to request the release of RAB. 

Release of all lu connection resources. This function is used to explicitly release all resources related to one lu 
connection. 

Requesting the release of all lu connection resources. While the lu release is managed from the CN, the RNC has 
the capability to request the release of all lu connection resources from the corresponding lu connection. 

SRNS context forwarding function. This function is responsible for transferring SRNS context from the RNC to 
the CN for intersystem change in case of packet forwarding. 

Controlling overload in the lu interface. This function allows adjusting the load in the lu interface. 

Resetting the lu. This function is used for resetting an lu interface. 

Sending the UE Common ID (permanent NAS UE identity) to the RNC. This function makes the RNC aware of 
the UE's Common ID. 

Paging the user. This function provides the CN for capability to page the UE. 

Controlling the tracing of the UE activity. This function allows setting the trace mode for a given UE. This 
function also allows the deactivation of a previously established trace. 

Transport of NAS information between UE and CN (see [8]). This function has two sub-classes: 

1. Transport of the initial NAS signalling message from the UE to CN. This function transfers transparently the 
NAS information. As a consequence also the lu signalling connection is set up. 

2. Transport of NAS signalling messages between UE and CN, This function transfers transparently the NAS 
signalling messages on the existing lu signalling connection. It also includes a specific service to handle 
signalling messages differently. 

Controlling the security mode in the UTRAN. This function is used to send the security keys (ciphering and 
integrity protection) to the UTRAN, and setting the operation mode for security functions. 

Controlling location reporting. This function allows the CN to operate the mode in which the UTRAN reports 
the location of the UE. 

Location reporting. This function is used for transferring the actual location information from RNC to the CN. 

Data volume reporting function. This function is responsible for reporting unsuccessfully transmitted DL data 
volume over UTRAN for specific RABs. 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



16 



ETSI TS 125 413 V4.10.0 (2003-09) 



Reporting general error situations. This function allows reporting of general error situations, for which function 
specific error messages have not been defined. 

Location related data. This function allows the CN to either retrieve from the RNC deciphering keys (to be 
forwarded to the UE) for the broadcasted assistance data, or request the RNC to deliver dedicated assistance data 
to the UE. 

These functions are implemented by one or several RANAP elementary procedures described in the following clause. 



8 



RANAP Procedures 



8.1 Elementary Procedures 



In the following tables, all EPs are divided into Class 1, Class 2 and Class 3 EPs (see subclause 3.1 for explanation of 
the different classes): 

Table 1 : Class 1 



Elementary 
Procedure 


Initiating 
IVIessage 


Successful Outcome 


Unsuccessful Outcome 


Response message 


Response message 


lu Release 


lU RELEASE 
COMMAND 


lU RELEASE COMPLETE 




Relocation 
Preparation 


RELOCATION 
REQUIRED 


RELOCATION COMMAND 


RELOCATION 
PREPARATION FAILURE 


Relocation 

Resource 

Allocation 


RELOCATION 
REQUEST 


RELOCATION REQUEST 
ACKNOWLEDGE 


RELOCATION FAILURE 


Relocation 
Cancel 


RELOCATION 
CANCEL 


RELOCATION CANCEL 
ACKNOWLEDGE 




SRNS Context 
Transfer 


SRNS CONTEXT 
REQUEST 


SRNS CONTEXT 
RESPONSE 




Security IVIode 
Control 


SECURITY 

MODE 

COMMAND 


SECURITY MODE 
COMPLETE 


SECURITY MODE REJECT 


Data Volume 
Report 


DATA VOLUME 

REPORT 

REQUEST 


DATA VOLUME REPORT 




Reset 


RESET 


RESET ACKNOWLEDGE 




Reset Resource 


RESET 
RESOURCE 


RESET RESOURCE 
ACKNOWLEDGE 




Location related 
Data 


LOCATION 
RELATED DATA 
REQUEST 


LOCATION RELATED 
DATA RESPONSE 


LOCATION RELATED DATA 
FAILURE 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



17 



ETSI TS 125 413 V4.10.0 (2003-09) 



Table 2: Class 2 



Elementary Procedure 


Message 


RAB Modification Request 


RAB MODIFY REQUEST 


RAB Release Request 


RAB RELEASE REQUEST 


lu Release Request 


lU RELEASE REQUEST 


Relocation Detect 


RELOCATION DETECT 


Relocation Complete 


RELOCATION COMPLETE 


SRNS Data Forwarding Initiation 


SRNS DATA FORWARD COMMAND 


SRNS Context Forwarding from 
Source RNC to CN 


FORWARD SRNS CONTEXT 


SRNS Context Forwarding to 
Target RNC from CN 


FORWARD SRNS CONTEXT 


Paging 


PAGING 


Common ID 


COMMON ID 


CN Invoke Trace 


CN INVOKE TRACE 


CN Deactivate Trace 


CN DEACTIVATE TRACE 


Location Reporting Control 


LOCATION REPORTING CONTROL 


Location Report 


LOCATION REPORT 


Initial UE IVIessage 


INITIAL UE MESSAGE 


Direct Transfer 


DIRECT TRANSFER 


Overload Control 


OVERLOAD 


Error Indication 


ERROR INDICATION 



Tables: Class 3 



Elementary Procedure 


Initiating Message 


Response Message 


RAB Assignment 


RAB ASSIGNMENT 
REQUEST 


RAB ASSIGNMENT 
RESPONSE xN{N>=1) 



The following applies concerning interference between Elementary Procedures: 

The Reset procedure takes precedence over all other EPs. 

The Reset Resource procedure takes precedence over all other EPs except the Reset procedure. 

The lu Release procedure takes precedence over all other EPs except the Reset procedure and the Reset Resource 
procedure. 

8.2 RAB Assignment 
8.2.1 General 

The purpose of the RAB Assignment procedure is to establish new RABs and/or to enable modifications and/or releases 
of already established RABs for a given UE. The procedure uses connection oriented signalling. 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



18 



ETSI TS 125 413 V4.10.0 (2003-09) 



8.2.2 Successful Operation 



RNC 



CN 



RAB ASSIGNMENT 
REQUEST 




* it can be several responses 

Figure 1: RAB Assignment procedure. Successful operation. 

The CN shall initiate the procedure by sending a RAB ASSIGNMENT REQUEST message. When sending the RAB 
ASSIGNMENT REQUEST message, the CN shall start the T RASAssgt timer. 

The CN may request UTRAN to: 

- establish, 
modify, 
release 

one or several RABs with one RAB ASSIGNMENT REQUEST message. 

The CN shall include in the RAB ASSIGNMENT REQUEST message at least one request to either estabUsh/modify or 
release a RAB. 

The message shall contain the information required by the UTRAN to build the new RAB configuration, such as: 

list of RABs to establish or modify with their bearer characteristics; 

list of RABs to release. 
For each RAB requested to establish, the message shall contain: 

- RAB ID. 

NAS Synchronisation Indicator (only when available). 

RAB parameters (including e.g. Allocation/Retention Priority). 

User Plane Information (i.e required User Plane Mode and required UP Mode Versions). 

Transport Layer Information. 

PDF Type Information (only for PS) 

Data Volume Reporting Indication (only for PS). 

DL GTP-PDU sequence number (only when GTP-PDU sequence number is available in cases of intersystem 
change from GPRS to UMTS or when establishing a RAB for an existing PDP context or in some further cases 
described in [21]). 

UL GTP-PDU sequence number (only when GTP-PDU sequence number is available in cases of intersystem 
change from GPRS to UMTS or when establishing a RAB for an existing PDP context or in some further cases 
described in [21]). 



£75/ 



3GPP TS 25.41 3 version 4.1 0.0 Release 4 1 9 ETSI TS 1 25 41 3 V4.1 0.0 (2003-09) 

DL N-PDU sequence number (only when N-PDU sequence number is available in case of intersystem change 
from GPRS to UMTS or in some further cases described in [21]). 

UL N-PDU sequence number (only when N-PDU sequence number is available in case of intersystem change 
from GPRS to UMTS or in some further cases described in [21]). 

For each RAB requested to modify, the message may contain: 

- RAB ID (mandatory). 

NAS Synchronisation Indicator. 

RAB parameters. 

Transport Layer Information. 

User Plane Information. 

The Transport Layer Information IE may be present at a RAB modification except in the case when the only other 
present IE, besides the RAB ID IE, is the NAS Synchronisation Indicator IE. 

At a RAB modification that does not include transfer of NAS Synchronisation Indicator IE, the RAB Parameters IE 
shall be present in RAB ASSIGNMENT REQUEST message only when any previously set value for this IE is 
requested to be modified. 

At a RAB modification, the User Plane Information IE shall be present in RAB ASSIGNMENT REQUEST message 
only when any previously set value for this IE is requested to be modified. 

For a RAB setup, the SDU Format Information Parameter IE in the RAB Parameters IE shall be present only if the 
User Plane Mode IE is set to "support mode for pre-defined SDU sizes" and the Traffic Class IE is set to either 
"Conversational" or "Streaming". 

If the RAB Parameters IE is present for a RAB modification, the SDU Format Information Parameter IE in the RAB 
Parameters IE shall be present only if the Traffic Class IE is set to either "Conversational" or "Streaming" and if 

- either the User Plane mode is currently "support mode for pre-defined SDU sizes" and the User Plane Mode IE 
is not contained in the RAB ASSIGNMENT REQUEST message 

- or if the User Plane Mode IE optionally contained within the RAB ASSIGNMENT REQUEST message is set to 
"support mode for pre-defined SDU sizes". 

If, for a RAB requested to be modified, one (or more) of these lEs except RAB ID IE are not present in RAB 
ASSIGNMENT REQUEST message the RNC shall continue to use the value(s) currently in use for the not present lEs. 

For each RAB request to release, the message shall contain: 

- RAB ID. 

Cause. 

Upon reception of the RAB ASSIGNMENT REQUEST message UTRAN shall execute the requested RAB 
configuration. The CN may indicate that RAB QoS negotiation is allowed for certain RAB parameters and in some 
cases also which alternative values to be used in the negotiation. 

The same RAB ID shall only be present once in the whole RAB ASSIGNMENT REQUEST message. 

The RAB ID shall identify uniquely the RAB for the specific CN domain for the particular UE, which makes the RAB 
ID unique over the lu connection on which the RAB ASSIGNMENT REQUEST message is received. When a RAB ID 
already in use over that particular lu instance is used, the procedure is considered as modification of that RAB. 

The RNC shall pass the contents of RAB ID IE to the radio interface protocol for each RAB requested to establish or 
modify. 

The RNC shall establish or modify the resources according to the values of the Allocation/Retention Priority IE 
(priority level, pre-emption indicators, queuing) and the resource situation as follows: 

The RNC shall consider the priority level of the requested RAB, when deciding on the resource allocation. 



£75/ 



3GPP TS 25.41 3 version 4.1 0.0 Release 4 20 ETSI TS 1 25 41 3 V4.1 0.0 (2003-09) 

If the requested RAB is allowed for queuing and the resource situation so requires, RNC may place the RAB in 
the establishment queue. 

The priority levels and the pre-emption indicators may (singularly or in combination) be used to determine 
whether the RAB assignment has to be performed unconditionally and immediately. If the requested RAB is 
marked as "may trigger pre-emption" and the resource situation so requires, RNC may trigger the pre-emption 
procedure which may then cause the forced release of a lower priority RAB which is marked as "pre-emptable". 
Whilst the process and the extent of the pre-emption procedure is operator dependent, the pre-emption indicators, 
if given in the RAB ASSIGNMENT REQUEST message, shall be treated as follows: 

1 . The values of the last received Pre-emption Vulnerability IE and Priority Level IE shall prevail. 

2. If the Pre-emption Capability IE is set to "may trigger pre-emption", then this allocation request may trigger 
the pre-emption procedure. 

3. If the Pre-emption Capability IE is set to "shall not trigger pre-emption", then this allocation request shall not 
trigger the pre-emption procedure. 

4. If the Pre-emption Vulnerability IE is set to "pre-emptable", then this connection shall be included in the pre- 
emption process. 

5. If the Pre-emption Vulnerability IE is set to "not pre-emptable", then this connection shall not be included in 
the pre-emption process. 

6. If the Priority Level IE is set to "no priority" the given values for the Pre-emption Capability IE and Pre- 
emption Vulnerability IE shall not be considered. Instead the values "shall not trigger pre-emption" and "not 
pre-emptable" shall prevail. 

- If the Allocation/Retention Priority IE is not given in the RAB ASSIGNMENT REQUEST message, the 
allocation request shall not trigger the pre-emption process and the connection may be pre-empted and 
considered to have the value "lowest" as priority level. Moreover, queuing shall not be allowed. 

The UTRAN pre-emption process shall keep the following rules: 

1 . UTRAN shall only pre-empt RABs with lower priority, in ascending order of priority. 

2. The pre-emption may be done for RABs belonging to the same UE or to other UEs. 

If the NAS Synchronisation Indicator IE is contained in the RAB ASSIGNMENT REQUEST message, the RNC shall 
pass it to the radio interface protocol for the transfer to the UE. 

If the RAB ASSIGNMENT REQUEST message includes the PDP Type Information IE, the UTRAN may use this to 
configure any compression algorithms. 

If the Service Handover IE is included, this tells if the RAB 

should be handed over to GSM, i.e. from NAS point of view, the RAB should be handed over to GSM as soon as 
possible although the final decision whether to perform a handover to GSM is still made in UTRAN. 

should not be handed over to GSM, i.e. from NAS point of view, the RAB should remain in UMTS as long as 
possible although the final decision whether to perform a handover to GSM is still made in UTRAN. 

shall not be handed over to GSM, i.e. the RAB shall never be handed over to GSM. This means that UTRAN shall 
not initiate handover to GSM for the UE unless the RABs with this indication have first been released with the 
normal release procedures. 

The value of the Service Handover IE is valid throughout the lifetime of the RAB or until changed by a RAB 
modification. 

The Service Handover IE shall only influence decisions made regarding UTRAN initiated inter-system handovers. 

If the Service Handover IE is not included, the decision whether to perform an inter-system handover to GSM is only an 
internal UTRAN matter. 

UTRAN shall report to CN, in the first RAB ASSIGNMENT RESPONSE message, the result for all the requested 
RABs, such as: 



£75/ 



3GPP TS 25.41 3 version 4.1 0.0 Release 4 21 ETSI TS 1 25 41 3 V4.1 0.0 (2003-09) 

List of RABs successfully established or modified. 

List of RABs released. 

List of RABs queued. 

List of RABs failed to establish or modify. 

List of RABs failed to release. 

The same RAB ID shall only be present once in the whole RAB ASSIGNMENT RESPONSE message. 

For each RAB successfully established towards the PS domain, the RNC shall include the Transport Layer Address IE 
and the lu Transport Association IE in the RAB ASSIGNMENT RESPONSE message. 

For each RAB successfully modified or released towards the PS domain, for which data volume reporting has been 
requested, the RNC shall include the DL Data Volumes IE in the RAB ASSIGNMENT RESPONSE message. 

For each RAB successfully released towards the PS domain, the RNC shall include in the RAB ASSIGNMENT 
RESPONSE message, if available, the DL GTP-PDU Sequence Number IE and the UL GTP-PDU Sequence Number 
IE, if the release was initiated by UTRAN. 

The RNC shall report in the RAB ASSIGNMENT RESPONSE message at least one RAB: 

setup/modified or 

released or 

queued or 

failed to setup/modify or 

failed to release. 

If any alternative RAB parameter values have been used when establishing or modifying a RAB, these RAB parameter 
values shall be included in the RAB ASSIGNMENT RESPONSE message within the Assigned RAB Parameter Values 
IE. 

For the CS domain, UTRAN shall report the successful outcome of a specific RAB to establish or modify only after the 
lu user plane at RNL level is ready to be used in UL and DL. At a RAB establishment, the transport network control 
plane signalling required to set up the transport bearer shall use the Transport Layer Address IE and lu Transport 
Association IE. At a RAB modification when Transport Layer Address IE and lu Transport Association IE is included, 
the RNC shall establish a new transport bearer. The transport network control plane signalling shall then use the 
included Transport Layer Address IE and lu Transport Association IE. Then the switch over to this new transport bearer 
shall be done immediately after transport bearer establishment and initialisation of the user plane mode. If Transport 
Layer Address IE and lu Transport Association IE is not included, then the RNC may modify the already existing 
transport bearer. 

For each RAB successfully modified towards the PS domain, if the RNC has changed the Transport Layer Address IE 
and/or the lu Transport Association IE, it shall include the new value(s) in the RAB ASSIGNMENT RESPONSE 

message. 

Before reporting the successful outcome of a specific RAB to establish or modify, the RNC shall have executed the 
initialisation of the user plane, if necessary. 

Re-initialisation of the user plane shall not be performed if: 

the RAB Parameters IE is not included, for example during transfer of NAS Synchronisation Indicator IE; 

the RAB Parameters IE is included but SDU Format Information Parameter IE is not changed for the existing RAB 
and NAS Synchronisation Indicator IE is not included. 

Re-initialisation of the user plane shall be performed if the RAB Parameters IE and NAS Synchronisation Indicator IE 
are included. 



£75/ 



3GPP TS 25.41 3 version 4.1 0.0 Release 4 22 ETSI TS 1 25 41 3 V4.1 0.0 (2003-09) 

If the RNC can not initialise the requested user plane mode for any of the user plane mode versions in the UP Mode 
Versions IE according to the rules for initialisation of the respective user plane mode versions, as described in [6], the 
RAB Assignment shall fail with the cause value "RNC unable to establish all RFCs". 

In case of establishment of a RAB for the PS domain, the CN must be prepared to receive user data before the RAB 
ASSIGNMENT RESPONSE message has been received. 

If none of the RABs have been queued, the CN shall stop timer T RABAssgt. And the RAB Assignment procedure 
terminates. In that case, the procedure shall also be terminated in UTRAN. 

When the request to establish or modify one or several RABs is put in the queue, UTRAN shall start the timer Tqueuing- 
This timer specifies the maximum time for queuing of the request of establishment or modification. The same timer 
Tqueuing is supervising all RABs being queued. 

For each RAB that is queued the following outcomes shall be possible: 

successfully established or modified; 

failed to establish or modify; 

failed due to expiry of the timer Tqueuing. 

For the queued RABs, indicated in the first RAB ASSIGNMENT RESPONSE message, UTRAN shall report the 
outcome of the queuing for every RAB individually or for several RABs in subsequent RAB ASSIGNMENT 
RESPONSE message(s). This is left to implementation. UTRAN shall stop Tqueuing when all RABs have been either 
successfully established or modified or failed to establish or modify. The RAB Assignment procedure is then terminated 
both in CN and UTRAN when all RABs have been responded to. 

When CN receives the response that one or several RABs are queued, CN shall expect UTRAN to provide the outcome 
of the queuing function for each RAB before expiry of the T RABAssgt timer. In case the timer T RABAssgt expires, the CN 
shall consider the RAB Assignment procedure terminated and the RABs not reported shall be considered as failed. 

In the case the timer Tqueuing expires, the RAB Assignment procedure terminates in UTRAN for all queued RABs, and 
UTRAN shall respond for all of them in one RAB ASSIGNMENT RESPONSE message. The RAB Assignment 
procedure shall also be terminated in CN. 

In case a request to modify or release a RAB contains the RAB ID of a RAB being queued, the RAB shall be taken out 
of the queue and treated according to the second request. The first request shall be responded to as a RAB failed to 
setup or modify with the cause value "Request superseded". 

If the UTRAN failed to modify a RAB it shall keep the RAB as it was configured prior to the modification request. 

When UTRAN reports unsuccessful establishment/modification of a RAB, the cause value should be precise enough to 
enable the core network to know the reason for unsuccessful establishment/modification. Typical cause values are: 
"Requested Traffic Class not Available", "Invalid RAB Parameters Value", "Requested Maximum Bit Rate not 
Available", "Requested Maximum Bit Rate for DL not Available", "Requested Maximum Bit Rate for UL not 
Available", "Requested Guaranteed Bit Rate not Available", "Requested Guaranteed Bit Rate for DL not Available", 
"Requested Guaranteed Bit Rate for UL not Available", "Requested Transfer Delay not Achievable", "Invalid RAB 
Parameters Combination", "Condition Violation for SDU Parameters", "Condition Violation for Traffic Handling 
Priority", "Condition Violation for Guaranteed Bit Rate", "User Plane Versions not Supported", "lu UP Failure", "lu 
Transport Connection Failed to Establish". 

If the RAB ID of a RAB requested to be released is unknown in the RNC, this shall be reported as a RAB failed to 
release with the cause value "Invalid RAB ID". 

The RNC may indicate an impending directed retry attempt to GSM by sending RAB ASSIGNMENT RESPONSE 
message with a RAB ID included in the list of RABs failed to setup and a cause value of "Directed Retry". 

The RNC shall be prepared to receive a RAB ASSIGNMENT REQUEST message containing a RABs To Be Released 
IE at any time and shall always reply to it. If there is an ongoing RAB Assignment procedure for a RAB indicated 
within the RABs To Be Released IE, the RNC shall discard the preceding RAB Assignment procedure for that specific 
RAB, release any related resources and report the released RAB within the RAB ASSIGNMENT RESPONSE message. 

After sending RAB ASSIGNMENT RESPONSE message containing RAB ID within the RABs Released IE, the RNC 
shall be prepared to receive new establishment request of a RAB identified by the same RAB ID. 



£75/ 



3GPP TS 25.41 3 version 4.1 0.0 Release 4 23 ETSI TS 1 25 41 3 V4.1 0.0 (2003-09) 

8.2.3 Unsuccessful Operation 

The unsuccessful operation for this Class 3 Elementary procedure is described under the Successful Operation chapter. 

8.2.4 Abnormal Conditions 

For a RAB requested to be modified, if only the RAB ID IE, the NAS Synchronisation Indicator IE and the Transport 
Layer Information IE are included in the First Setup or Modify Item IE this RAB shall not be modified, and the 
corresponding RAB ID IE with Cause IE shall be included in the "RABs Failed To Setup Or Modify List" in the RAB 
ASSIGNMENT RESPONSE message. 

If, for a RAB requested to be setup towards the PS domain, any of these following lEs: 

PDF Type Information. 

Data Volume Reporting Indication. 

is not present, the RNC shall continue with the procedure. 

Interactions with Relocation Preparation procedure: 

If the relocation becomes necessary during the RAB Assignment procedure, the RNC may interrupt the ongoing RAB 
Assignment procedure and initiate the Relocation Preparation procedure as follows: 

1 . The RNC shall terminate the RAB Assignment procedure indicating unsuccessful RAB configuration 
modification: 

for all queued RABs; 

for RABs not already established or modified, and 

for RABs not already released; 

with the cause "Relocation triggered". 

2. The RNC shall terminate the RAB Assignment procedure indicating successful RAB configuration modification: 

for RABs already established or modified but not yet reported to the CN, and 
for RABs already released but not yet reported to the CN. 

3. The RNC shall report this outcome of the procedure in one RAB ASSIGNMENT RESPONSE message. 

4. The RNC shall invoke relocation by sending the RELOCATION REQUIRED message to the active CN node(s). 

5. The CN shall terminate the RAB Assignment procedure at reception of the RAB ASSIGNMENT RESPONSE 
message. 

Directed retry from UMTS to GSM (CS domain only): 

In the case where the RNC has no RAB configuration for a particular UE in the CS domain, and the RNC receives a 
RAB ASSIGNMENT REQUEST message for that UE requesting the establishment of one RAB only, a directed retry 
to perform inter-system handover to GSM may be initiated. In this case the RNC may interrupt the ongoing RAB 
Assignment procedure and initiate the Relocation Preparation procedure as follows: 

1 . The RNC shall terminate the RAB Assignment procedure indicating unsuccessful RAB configuration 
modification of that RAB with the cause "Directed retry". 

2. The RNC shall report this outcome of the procedure in one RAB ASSIGNMENT RESPONSE message. 

3. The RNC shall invoke relocation by sending the RELOCATION REQUIRED message to the active CN node, 
with the cause "Directed Retry". 

4. The CN shall terminate the RAB Assignment procedure at reception of the RAB ASSIGNMENT RESPONSE 
message. 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



24 



ETSI TS 125 413 V4.10.0 (2003-09) 



8.3 RAB Release Request 

8.3.1 General 

The purpose of the RAB Release Request procedure is to enable UTRAN to request the release of one or several radio 
access bearers. The procedure uses connection oriented signalling. 

8.3.2 Successful Operation 



RNC 



CN 



RAB 

RELEASE REQUEST 

► 



Figure 2: RAB Release Request procedure. Successful operation. 

The RNC shall initiate the procedure by generating a RAB RELEASE REQUEST message towards the CN. The RABs 
To Be Released IE shall indicate the list of RABs requested to release and the Cause IE associated to each RAB shall 
indicate the reason for the release, e.g. "RAB pre-empted", "Release due to UTRAN Generated Reason", "Radio 
Connection With UE Lost". 

Upon reception of the RAB RELEASE REQUEST message, the CN should initiate the appropriate release procedure 
for the identified RABs in the RAB RELEASE REQUEST message. It is up to the CN to decide how to react to the 
request. 

Interaction witli lu Release Command: 

If no RABs will remain according to the RAB RELEASE REQUEST message, the CN may decide to initiate the lu 
Release procedure if it does not want to keep the lu signalling connection. The cause value to use is "No Remaining 
RAB". 

Interaction with RAB Assignment (release RAB): 

If the CN decides to release some or all indicated RABs, the CN may decide to invoke the RAB Assignment procedure 
(release RAB) to this effect. 

8.3.3 Abnormal Concditions 

Not appUcable. 

8.4 lu Release Request 
8.4.1 General 

The purpose of the lu Release Request procedure is to enable UTRAN to request the CN to release the lu connection for 
a particular UE due to some UTRAN generated reason (e.g. "O&M Intervention", "Unspecified Failure", "User 
Inactivity", "Repeated Integrity Checking Failure" , "Release due to UE generated signalling connection release", 
"Radio Connection With UE Lost"). The procedure uses connection oriented signalling. 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



25 



ETSI TS 125 413 V4.10.0 (2003-09) 



8.4.2 Successful Operation 



RNC 



CN 



lU RELEASE REQUEST 



Figure 3: lu Release Request procedure. Successful operation. 

The RNS controlling the lu connection(s) of that particular UE shall initiate the procedure by generating an lU 
RELEASE REQUEST message towards the affected CN domain(s). The procedure may be initiated for instance when 
the contact with a particular UE is lost or due to user inactivity. 

The lU RELEASE REQUEST message shall indicate the cause value for the requested lu connection release. It is up to 
the CN to decide how to react to the request. 

Interactions with lu Release procedure: 

The lu Release procedure should be initiated upon reception of lU RELEASE REQUEST message when the cause is 
different than "User Inactivity". When the cause is set to "User Inactivity", it is optional to initiate the lu Release 
procedure. 

8.4.3 Abnormal Conditions 

Not appUcable. 



8.5 



lu Release 



8.5.1 General 

The purpose of the lu Release procedure is to enable the CN to release the lu connection and all UTRAN resources 
related only to that lu connection to be released. The procedure uses connection oriented signalling. 

The lu Release procedure can be initiated for at least the following reasons: 

Completion of transaction between UE and CN. 

UTRAN generated reasons, e.g. reception of lU RELEASE REQUEST message. 

Completion of successful relocation of SRNS. 

Cancellation of relocation after successful completion of the Relocation Resource Allocation procedure. 
The lu release procedure should also be initiated when there is a period of lu signalling inactivity with no existing RAB. 



8.5.2 Successful Operation 

RNC 



CN 



lU RELEASE COMMAND 



lU RELEASE COMPLETE 



Figure 4: lu Release procedure. Successful operation. 



£75/ 



3GPP TS 25.41 3 version 4.1 0.0 Release 4 26 ETSI TS 1 25 41 3 V4.1 0.0 (2003-09) 

The procedure is initiated by the CN by sending an lU RELEASE COMMAND message to the UTRAN. 

After the lU RELEASE COMMAND message has been sent, the CN shall not send further RANAP connection 
oriented messages on this particular connection. 

The lU RELEASE COMMAND message shall include a Cause IE, indicating the reason for the release 

(e.g. "Successful Relocation", "Normal Release", "Release due to UTRAN Generated Reason", "Relocation Cancelled", 

"No Remaining RAB"). 

When the RNC receives the lU RELEASE COMMAND message: 

1 . Clearing of the related UTRAN resources is initiated. However, the UTRAN shall not clear resources related to 
other lu signalling connections the UE might have. The lu transport bearers for RABs subject to data forwarding 
and other UTRAN resources used for the GTP-PDU forwarding process, are released by the RNC only when the 
timer ToATAfwd expires. 

2. The RNC returns any assigned lu user plane resources to idle i.e. neither uplink user data nor downlink user data 
can be transferred over the lu interface anymore. Then the RNC sends an lU RELEASE COMPLETE message 
to the CN. (The RNC does not need to wait for the release of UTRAN radio resources or for the transport 
network layer signalling to be completed before returning the lU RELEASE COMPLETE message.) When an 
lU RELEASE COMPLETE message is sent, the procedure is terminated in the UTRAN. 

The lU RELEASE COMPLETE message shall include a RABs Data Volume Report IE for RABs towards the PS 
domain for which data volume reporting was requested during RAB establishment. 

If the release was initiated by UTRAN, for each RAB towards the PS domain, for which the DL GTP-PDU Sequence 
Number IE and/or the UL GTP-PDU Sequence Number IE are (is) available, the RNC shall include the available 
sequence number(s) in the RABs Released Item IE (within the RAB Released List IE) in the lU RELEASE COMPLETE 

message. 

The RAB Release Item IE shall not be present if there is no sequence number to be reported for that RAB. 
Reception of an lU RELEASE COMPLETE message terminates the procedure in the CN. 

8.5.3 Abnormal Conditions 

If the lu Release procedure is not initiated towards the source RNC from the CN before the expiry of timer TRELocoveraii, 
the source RNC should initiate the lu Release Request procedure towards the CN with a cause value "TRELocoveraii 
expiry" . 

8.6 Relocation Preparation 
8.6.1 General 

The purpose of the Relocation Preparation procedure is to prepare relocation of SRNS either with involving UE or 
without involving UE. The relocation procedure shall be co-ordinated in all lu signalling connections existing for the 
UE in order to allow Relocation co-ordination in the target RNC. The procedure uses connection oriented signalling. 

The source RNC shall not initiate the Relocation Preparation procedure for an lu signalling connection if a Prepared 
Relocation exists in the RNC for that lu signalling connection or if a Relocation Preparation procedure is ongoing for 
that lu signalling connection. 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



27 



ETSI TS 125 413 V4.10.0 (2003-09) 



8.6.2 Successful Operation 



Source RNC 



CN 



RELOCATION REOUIRED 



RELOCATION COMMAND 



Figure 5: Relocation Preparation procedure. Successful operation. 

The source RNC shall initiate the procedure by generating RELOCATION REQUIRED message. The source RNC 
shall decide whether to initiate the intra-system Relocation or the inter-system handover. In case of intra-system 
Relocation the source RNC shall indicate in the Source ID IE the RNC-ID of the source RNC and in the Target ID IE 
the RNC-ID of the target RNC. In case of inter-system handover the source RNC shall indicate in the Source ID IE the 
Service Area Identifier and in the Target ID IE the cell global identity of the cell in the target system. The source RNC 
shall indicate the appropriate cause value for the Relocation in the Cause IE. Typical cause values are "Time critical 
Relocation", "Resource optimisation relocation", "Relocation desirable for radio reasons" , "Directed Retry". 

The source RNC shall determine whether the relocation of SRNS shall be executed with or without involvement of UE. 
The source RNC shall set the Relocation Type IE accordingly to "UE involved in relocation of SRNS " or "UE not 
involved in relocation of SRNS ". 

In case of intra-system Relocation, the source RNC shall include in the RELOCATION REQUIRED message the 
Source RNC to Target RNC Transparent Container IE. This container shall include the Relocation Type IE and the 
number of lu signalling connections existing for the UE by setting correctly the Number oflu Instances IE. 

Only in case of intra-system relocation, the Source RNC-to-Target RNC transparent container IE shall include the 
Integrity Protection Key IE from the last received domain on which security mode control procedure has been 
successfully performed and the associated Chosen Integrity Protection Algorithm IE that has been selected for this 
domain. 

Only in case of intra-system relocation, the Source RNC-to-Target RNC transparent container IE shall include the 
Ciphering Key IE for the signalling data from the last received domain on which security mode control procedure has 
been successfully performed and the associated Chosen Encryption Algorithm IE that has been selected for this domain. 

Only in case of intra-system relocation, for each domain where the security mode control procedure has been 
successfully performed in the source RNC, the Source RNC-to-Target RNC transparent container IE shall include the 
Chosen Encryption Algorithm IE of CS (PS respectively) user data corresponding to the ciphering alternative that has 
been selected for this domain. If the security mode control procedure had not been successful or performed for one 
domain or had proposed no ciphering alternative, the Chosen Encryption Algorithm IE for the user data of this domain 
shall not be included. When both the CS and the PS user data Chosen Encryption Algorithm lEs are provided, they shall 
be the same. 

This Source RNC-to-Target RNC transparent container IE shall include the RRC Container IE. If the Relocation Type 
IE is set to "UE not involved in relocation of SRNS" and the UE is using DCH(s), DSCH(s) or USCH(s), the Source 
RNC to Target RNC Transparent Container IE shall: 

for each RAB include the RAB ID, the CN Domain Indicator IE and the mapping between each RAB subflow 
and transport channel identifier(s) over lur, i.e. if the RAB is carried on a DCH(s), the DCH ID(s) shall be 
included, and when it is carried on DSCH(s) or USCH(s), the DSCH ID(s) or USCH ID(s) respectively shall 
be included, 

only in the case the active SRBs in SRNC are not all mapped onto the same DCH, include the SRB TrCH 
Mapping IE containing for each SRB the SRB ID and the associated transport channel identifier over lur, i.e. 
if the SRB is carried on a DCH, the DCH ID shall be included, and when it is carried on DSCH or USCH, the 
DSCH ID or USCH ID respectively shall be included. 



£75/ 



3GPP TS 25.41 3 version 4.1 0.0 Release 4 28 ETSI TS 1 25 41 3 V4.1 0.0 (2003-09) 

If the Relocation Type IE is set to "UE not involved in relocation of SRNS", the d-RNTI IE shall be included in the 
Source RNC to Target RNC Transparent Container IE. If the Relocation Type IE is set to "UE involved in relocation of 
SRNS", the Target Cell ID IE shall be included in the Source RNC to Target RNC Transparent Container IE. 

In case of inter-system handover to GSM the RNC: 

shall include MS Classmark 2 and MS Classmark 3 lEs received from the UE in the RELOCATION 
REQUIRED message to the CN. 

shall include the Old BSS to New BSS IE within the RELOCATION REQUIRED message only if the 
information is available. 

The source RNC shall send the RELOCATION REQUIRED message to the CN and the source RNC shall start the 
timer TRELocprep. 

When the preparation including resource allocation in the target system is ready and the CN has decided to continue the 
relocation of SRNS, the CN shall send RELOCATION COMMAND message to the source RNC and the CN shall start 
the timer TRELoccompiete- 

If the Target RNC To Source RNC Transparent Container IE or the L3 information IE is received by the CN from the 
relocation target, it shall be included in the RELOCATION COMMAND message. 

For each RAB successfully established in the target system and originating from the PS domain, the RELOCATION 
COMMAND message shall contain lu transport address and lu transport association to be used for the forwarding of the 
DL N-PDU duplicates towards the relocation target. Upon reception of the RELOCATION COMMAND message from 
the PS domain, the source RNC shall start the timer ToAXAfwd. 

The Relocation Preparation procedure is terminated in the CN by transmission of RELOCATION COMMAND 

message. 

If the target system (including target CN) does not support all existing RABs, the RELOCATION COMMAND 
message shall contain a list of RABs indicating all the RABs that are not supported by the target system. This list is 
contained in the RABs to Be Released IE. The source RNC shall use this information to avoid transferring associated 
contexts where applicable and may use this information e.g. to decide if to cancel the relocation or not. The resources 
associated with these not supported RABs shall not be released until the relocation is completed. This is in order to 
make a return to the old configuration possible in case of a failed or cancelled relocation. 

Upon reception of RELOCATION COMMAND message the source RNC shall stop the timer TRELocprep, RNC shall 
start the timer TRELocoveraii and RNC shall terminate the Relocation Preparation procedure. The source RNC is then 
defined to have a Prepared Relocation for that lu signalling connection. 

When Relocation Preparation procedure is terminated successfully and when the source RNC is ready, the source RNC 
should trigger the execution of relocation of SRNS. 

Interactions with other procedures: 

If, after RELOCATION REQUIRED message is sent and before the Relocation Preparation procedure is terminated, the 
source RNC receives a RANAP message initiating an other connection oriented RANAP class 1 or class 3 procedure 
(except lU RELEASE COMMAND message, which shall be handled normally) via the same lu signalling connection, 
the source RNC shall either: 

1. cancel the Relocation Preparation procedure i.e. execute Relocation Cancel procedure with an appropriate value 
for the Cause IE, e.g. "Interaction with other procedure", and after successful completion of Relocation Cancel 
procedure, the source RNC shall continue the initiated RANAP procedure; 

or 

2. terminate the initiated RANAP procedure without any changes in UTRAN by sending appropriate response 
message with the cause value "Relocation Triggered" to the CN. The source RNC shall then continue the 
relocation of SRNS. 

If during the Relocation Preparation procedure the source RNC receives a DIRECT TRANSFER message it shall be 
handled normally. 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



29 



ETSI TS 125 413 V4.10.0 (2003-09) 



If during the Relocation Preparation procedure the source RNC receives connection oriented RANAP class 2 messages 
(with the exception of DIRECT TRANSFER message) it shall decide to either execute the procedure immediately or 
suspend it. In the case the relocation is cancelled the RNC shall resume any suspended procedures (if any). 

After Relocation Preparation procedure is terminated successfully, all RANAP messages (except lU RELEASE 
COMMAND message, which shall be handled normally) received via the same lu signalling bearer shall be ignored by 
the source RNC. 



8.6.3 Unsuccessful Operation 



Source RNC 



CN 



RELOCATION REOUIRED 



RELOCATION PREPARATION 
FAILURE 



Figure 6: Relocation Preparation procedure. Unsuccessful operation. 

If the CN or target system is not able to even partially accept the relocation of SRNS or a failure occurs during the 
Relocation Preparation procedure in the CN or the CN decides not to continue the relocation of SRNS, the CN shall 
send RELOCATION PREPARATION FAILURE message to the source RNC. 

RELOCATION PREPARATION FAILURE message shall contain appropriate value for the Cause IE e.g. "TRELocaiioc 
expiry", "Relocation Failure in Target CN/RNC or Target System"., "Relocation not supported in Target RNC or Target 
System", "Relocation Target not allowed". 

Transmission of RELOCATION PREPARATION FAILURE message terminates the procedure in the CN. Reception 
of RELOCATION PREPARATION FAILURE message terminates the procedure in UTRAN. 

When the Relocation Preparation procedure is unsuccessfully terminated, the existing lu signalling connection can be 
used normally. 

If the Relocation Preparation procedure is terminated unsuccessfully, the CN shall release the possibly existing lu 
signalling connection for the same UE and related to the same relocation of SRNS towards the target RNC by initiating 
lu Release procedure towards the target RNC with an appropriate value for the Cause IE, e.g. "Relocation Cancelled". 

Interactions with Relocation Cancel procedure: 

If there is no response from the CN to the RELOCATION REQUIRED message before timer TRELocprep expires in the 
source RNC, the source RNC shall cancel the Relocation Preparation procedure by initiating the Relocation Cancel 
procedure with appropriate value for the Cause IE, e.g. "TRELocprep expiry". 

8.6.4 Abnormal Conditions 

If the target RNC, which was indicated in the RELOCATION REQUIRED message, is not known to the CN: 

1 . The CN shall reject the relocation of SRNS by sending a RELOCATION PREPARATION FAILURE message 
to the source RNC with Cause IE set to "Unknown target RNC". 

2. The CN shall continue to use the existing lu connection towards the source RNC. 

NOTE: In case two CN domains are involved in the SRNS Relocation Preparation procedure and the Source RNC 
receives the Target RNC to Source RNC Transparent Container IE via two CN domains, it may check 
whether the content of the two Target RNC to Source RNC Transparent Container IE is the same. In case 
the Source RNC receives two different Target RNC to Source RNC Transparent Container IE, the RNC 
behaviour is left implementation specific. 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



30 



ETSI TS 125 413 V4.10.0 (2003-09) 



8.6.5 Co-ordination of Two lu Signalling Connections 

If the RNC has decided to initiate Relocation Preparation procedure for a UTRAN to UTRAN relocation, the RNC shall 
initiate simultaneously Relocation Preparation procedure on all lu signalling connections existing for the UE. The 
source RNC shall also include the same Source RNC to Target RNC Transparent Container IE, Relocation Type IE, 
Source ID IE and Cause IE in the RELOCATION REQUIRED message towards the two domains. 

For intersystem handover to GSM, Relocation Preparation procedure shall be initiated only towards the circuit switched 
CN. 

The source RNC shall not trigger the execution of relocation of SRNS unless it has received RELOCATION 
COMMAND message from all lu signalling connections for which the Relocation Preparation procedure has been 
initiated. 

If the source RNC receives RELOCATION PREPARATION FAILURE message from the CN, the RNC shall initiate 
Relocation Cancel procedure on the other lu signalling connection for the UE if the other lu signalling connection exists 
and if the Relocation Preparation procedure is still ongoing or the procedure has terminated successfully in that lu 
signalling connection. 

8.7 Relocation Resource Allocation 

8.7.1 General 

The purpose of the Relocation Resource Allocation procedure is to allocate resources from target RNS for a relocation 
of SRNS. Procedure shall be co-ordinated in all lu signalling connections existing for the UE. The procedure uses 
connection oriented signalling. 

8.7.2 Successful Operation 



Target RNC 



CN 



RELOCATION REQUEST 



RELOCATION REQUEST 
ACKNOWLEDGE 



Figure 7: Relocation Resource Allocation procedure. Successful operation. 

The CN shall initiate the procedure by generating RELOCATION REQUEST message. In a UTRAN to UTRAN 
relocation, this message shall contain the information (if any) required by the UTRAN to build the same set of RABs as 
existing for the UE before the relocation. The CN may indicate that RAB QoS negotiation is allowed for certain RAB 
parameters and in some cases also which alternative values to be used in the negotiation. 

The CN shall transmit the RELOCATION REQUEST message to target RNC and the CN shall start the timer 

TRELOCalloc. 

When a RELOCATION REQUEST message is sent from a CN node towards an RNC for which the sending CN node 
is not the default CN node, the Global CN-ID IE shall be included. 

Upon reception of the RELOCATION REQUEST message, the target RNC shall initiate allocation of requested 
resources. 



£75/ 



3GPP TS 25.41 3 version 4.1 0.0 Release 4 31 ETSI TS 1 25 41 3 V4.1 0.0 (2003-09) 

The RELOCATION REQUEST message shall contain following lEs 

Permanent NAS UE Identity IE (if available) 

Cause 

CN Domain Indicator 

Source RNC To Target RNC Transparent Container 

lu Signalling Connection Identifier 

Integrity Protection Information IE (if available) 

For each RAB requested to relocate (or to be created e.g. in the case of inter-system handover), the message shall 
contain following lEs: 

- RAB-ID 

- NAS Synchronisation Indicator IE (if the relevant NAS information is provided by the CN) 
RAB parameters 

User Plane Information 

Transport Layer Address 

lu Transport Association 

Data Volume Reporting Indication (only for PS) 

PDP Type Information (only for PS) 
The RELOCATION REQUEST message may include following lEs: 

Encryption Information (shall not be included if the Integrity Protection Information IE is not included) 
For each RAB requested to relocate the message may include following lEs: 

Service Handover. 

Alternative RAB Parameter Values. 

The following information elements received in RELOCATION REQUEST message require the same special actions in 
the RNC as specified for the same lEs in the RAB Assignment procedure: 

- RAB-ID 

User plane Information(i.e. required User Plane Mode and required User Plane Versions) 

Priority level, queuing and pre-emption indication 

Service Handover 

The SDU Format Information Parameter IE in the RAB Parameters IE shall be present only if the User Plane Mode IE 
is set to "support mode for pre-defmed SDU sizes" and the Traffic Class IE is set to either "Conversational" or 
"Streaming". 

If the RELOCATION REQUEST message includes the PDP Type Information IE, the UTRAN may use this IE to 
configure any compression algorithms. 

The Cause IE shall contain the same value as the one received in the related RELOCATION REQUIRED message. 

The lu Signalling Connection Identifier IE contains an lu signalling connection identifier which is allocated by the CN. 
The value for the lu Signalling Connection Identifier IE shall be allocated so as to uniquely identify an lu signalling 
connection for the CN node involved. The RNC shall store and remember this identifier for the duration of the lu 
connection. 



£75/ 



3GPP TS 25.41 3 version 4.1 0.0 Release 4 32 ETSI TS 1 25 41 3 V4.1 0.0 (2003-09) 

The algorithms within the Integrity Protection Information IE and the Encryption Information IE shall be ordered in 
preferred order with the most preferred first in the list. 

The Permitted Encryption Algorithms IE within the Encryption Information IE may contain "no encryption" within an 
element of its list in order to allow the RNC not to cipher the respective connection. This can be done either by not 
starting ciphering or by using the UEAO algorithm. In the absence of the Encryption Information IE, the RNC shall not 
start ciphering. 

In case of intra-system relocation, if no Integrity Protection Key IE {Ciphering Key IE respectively) is provided within 
the Source RNC-to-Target RNC transparent container IE, the target RNC shall not start integrity protection (ciphering 
respectively). 

In case of intra-system relocation, when an Ciphering Key IE is provided within the Source RNC-to-Target RNC 
transparent container IE, the target RNC may select to use a ciphering alternative where an algorithm is used. It shall in 
this case make use of this key to cipher its signalling data whatever the selected algorithm. The Encryption Key IE that 
is contained within the Encryption Information IE of the RELOCATION REQUEST message shall never be considered 
for ciphering of signalling data. 

In case of intra-system relocation, when an Integrity Protection Key IE is provided within the Source RNC-to-Target 
RNC transparent container IE, the target RNC shall select one integrity algorithm to start integrity and shall in this case 
make use of this key whatever the selected algorithm. The integrity protection key that is contained within the Integrity 
Protection Information IE of the RELOCATION REQUEST message shall never be considered. 

In case of inter-system relocation, the integrity protection and ciphering information to be considered shall be the ones 
received in the Integrity Protection Information IE and Encryption Information IE from the RELOCATION REQUEST 
messages over the lu interface. 

The Global CN-ID IE contains the identity of the CN node that sent the RELOCATION REQUEST message, and it 
shall, if included, be stored together with the lu signalling connection identifier. If the Global CN-ID IE is not included, 
the RELOCATION REQUEST message shall be considered as coming from the default CN node for the indicated CN 
domain. 

Following additional actions shall be executed in the target RNC during Relocation Resource Allocation procedure: 

If the Relocation Type IE is set to "UE involved in relocation of SRNS": 

The target RNC may accept a requested RAB only if the RAB can be supported by the target RNC. 

- Other RABs shall be rejected by the target RNC in the RELOCATION REQUEST ACKNOWLEDGE message 
with an appropriate value for Cause IE, e.g. "Unable to Establish During Relocation". 

The target RNC shall include information adapted to the resulting RAB configuration in the target to source 
RNC transparent container to be included in the RELOCATION REQUEST ACKNOWLEDGE message sent to 
the CN. If the target RNC supports triggering of the Relocation Detect procedure via the lur interface, the RNC 
shall assign a d-RNTI for the context of the relocation and include it in the container. If two CNs are involved in 
the relocation of SRNS, the target RNC may, however, decide to send the container to only one CN. 

If any alternative RAB parameter values have been used when allocating the resources, these RAB parameter 
values shall be included in the RELOCATION REQUEST ACKNOWLEDGE message within \h& Assigned RAB 
Parameter Values IE. 

If the Relocation Type IE is set to "UE not involved in relocation of SRNS": 

The target RNC may accept a RAB only if the radio bearer(s) for the RAB either exist(s) already, and can be 
used for the RAB by the target RNC, or does not exist before the relocation but can be established in order to 
support the RAB in the target RNC. 

If existing radio bearers are not related to any RAB that is accepted by target RNC, the radio bearers shall be 
ignored during the relocation of SRNS and the radio bearers shall be released by radio interface protocols after 
completion of relocation of SRNS. 

If any alternative RAB parameter values have been used when allocating the resources, these RAB parameter 
values shall be included in the RELOCATION REQUEST ACKNOWLEDGE message within Xhe Assigned RAB 
Parameter Values IE. It should be noted that the usage of alternative RAB parameter values is not applicable to 
the UTRAN initiated relocation of type "UE not involved in relocation of SRNS". 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



33 



ETSI TS 125 413 V4.10.0 (2003-09) 



After all necessary resources for accepted RABs including the initialised lu user plane, are successfully allocated, the 
target RNC shall send RELOCATION REQUEST ACKNOWLEDGE message to the CN. 

For each RAB successfully setup the RNC shall include following lEs: 

- RABID 

Transport Layer Address (only for PS) 

lu Transport Association (only for PS) 

For each RAB the RNC is not able to setup during Relocation Resource Allocation the RNC shall include the RAB ID 
IE and the Cause IE within the RABs Failed To Setup IE. The resources associated with the RABs indicated as failed to 
set up shall not be released in the CN until the relocation is completed. This is in order to make a return to the old 
configuration possible in case of a failed or cancelled relocation. 

The RELOCATION REQUEST ACKNOWLEDGE message sent to the CN shall, if applicable and if not sent via the 
other CN domain, include the Target RNC To Source RNC Transparent Container IE. This container shall be 
transferred by CN to the source RNC or the external relocation source while completing the Relocation Preparation 
procedure. 

The RNC shall include the Chosen Integrity Protection Algorithm IE (Chosen Encryption Algorithm IE respectively) 
within the RELOCATION REQUEST ACKNOWLEDGE message, if, and only if the Integrity Protection Information 
IE {Encryption Information IE respectively) was included in the RELOCATION REQUEST message. 

If one or more of the RABs that the target RNC has decided to support can not be supported by the CN, then these 
failed RABs shall not be released towards the target RNC until the relocation is completed. 

If the NAS Synchronisation Indicator IE is contained in the RELOCATION REQUEST message, the target RNC shall 
pass it to the UE. 

Transmission and reception of RELOCATION REQUEST ACKNOWLEDGE message terminates the procedure in the 
UTRAN and the CN respectively. 

Before reporting the successful outcome of the Relocation Resource allocation procedure, the RNC shall have executed 
the initialisation of the user plane mode as requested by the CN in the User Plane Mode IE. If the RNC can not initialise 
the requested user plane mode for any of the user plane mode versions in the UP Mode Versions IE according to the 
rules for initialisation of the respective user plane mode versions, as described in [6], the RAB Relocation shall fail with 
the cause value "RNC unable to establish all RFCs". 



8.7.3 Unsuccessful Operation 

Target RNC 



CN 



RELOCATION REOUEST 



RELOCATION FAILURE 



Figure 8: Relocation Resource Allocation procedure: Unsuccessful operation. 

If the target RNC can not even partially accept the relocation of SRNS or a failure occurs during the Relocation 
Resource Allocation procedure in the target RNC, the target RNC shall send RELOCATION FAILURE message to the 
CN. 



£75/ 



3GPP TS 25.41 3 version 4.1 0.0 Release 4 34 ETSI TS 1 25 41 3 V4.1 0.0 (2003-09) 

If the target RNC cannot support any of the integrity protection (ciphering respectively) ahernatives provided in the 
Integrity Protection Information IE {Encryption Information IE respectively), it shall return a RELOCATION 
FAILURE message with the cause "Requested Ciphering and/or Integrity Protection algorithms not supported". 

Transmission and reception of RELOCATION FAILURE message terminates the procedure in the UTRAN and the CN 
respectively. 

When CN has received RELOCATION FAILURE message from target RNC, CN shall stop timer TRELocaiioc and shall 
assume possibly allocated resources within target RNC completely released. 

8.7.4 Abnormal Conditions 

If after reception of the RELOCATION REQUEST message, the target RNC receives another RELOCATION 
REQUEST message on the same lu connection, then the target RNC shall discard the latter message and the original 
Relocation Resource Allocation procedure shall continue normally. 

If the target RNC receives a Source RNC -to-Target RNC Transparent Container IE containing Chosen Integrity 
Protection (Encryption respectively) Algorithm IE without Integrity Protection (Ciphering respectively) Key IE, it shall 
return RELOCATION FAILURE message with the cause "Conflict with already existing Integrity protection and/or 
Ciphering information". 

NOTE: In case two CN domains are involved in the SRNS Relocation Resource Allocation procedure, the Target 
RNC may check whether the content of the two Source RNC to Target RNC Transparent Container IE is 
the same. In case the Target RNC receives two different Source RNC to Target RNC Transparent 
Container IE, the RNC behaviour is left implementation specific. 

Interactions with lu Release procedure: 

If the CN decides to not continue the Relocation Resource Allocation procedure (e.g. due to TRELocaiioc expiry) before 
the Relocation Resource Allocation procedure is completed, the CN shall stop timer TRELocaiioc (if timer TRELocaiioc has 
not already expired) and the CN shall, if the lu signalling connection has been established or later becomes established, 
initiate the lu Release procedure towards the target RNC with an appropriate value for the Cause IE, e.g. "Relocation 
Cancelled". 

8.7.5 Co-ordination of Two lu Signalling Connections 

Co-ordination of two lu signalling connections during Relocation Resource Allocation procedure shall be executed by 
the target RNC when the Number oflu Instances IE received in the Source RNC to Target RNC Transparent Container 
IE in the RELOCATION REQUEST message indicates that two CN domains are involved in relocation of SRNS. 

When both the CS and PS user data Chosen Encryption Algorithm IE are received within the Source RNC-to-Target 
RNC transparent container IE and if these two received Chosen Encryption Algorithm IE are not the same, the target 
RNC shall fail the Relocation Resource Allocation procedure by sending back the RELOCATION FAILURE message. 

The integrity protection (ciphering respectively) alternatives provided in the Integrity Protection Information IE 
(Encryption Information IE respectively) of the RELOCATION REQUEST messages received from both CN domains 
shall have at least one common alternative, otherwise the Relocation Resource Allocation shall be failed by sending 
back the RELOCATION FAILURE message. 

If two CN domains are involved, the following actions shall be taken by the target RNC: 

The target RNC shall utilise the Permanent NAS UE Identity IE, received explicitly by each CN domain within 
RELOCATION REQUEST message, to co-ordinate both lu signalling connections. 

- The target RNC shall generate and send RELOCATION REQUEST ACKNOWLEDGE message only after all 
expected RELOCATION REQUEST messages are received and analysed. 

If the target RNC decides to send the Target RNC to Source RNC Transparent Container IE via the two CN 
domains, the target RNC shall ensure that the same Target RNC to Source RNC Transparent Container IE is 
included in RELOCATION REQUEST ACKNOWLEDGE messages transmitted via the two CN domains and 
related to the same relocation of SRNS. 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



35 



ETSI TS 125 413 V4.10.0 (2003-09) 



8.8 



Relocation Detect 



8.8.1 General 

The purpose of Relocation Detect procedure is to indicate by the RNC the detection of SRNS relocation execution to 
the CN. Procedure shall be co-ordinated in all lu signalling connections existing for the UE. The procedure uses 
connection oriented signalling. 

8.8.2 Successful Operation 



Target RNC 



CN 



RELOCATION DETECT 



Figure 9: Relocation Detect procedure: Successful operation. 

The target RNC shall send RELOCATION DETECT message to the CN when relocation execution trigger is received. 

If the type of relocation of SRNS is "UE involved in relocation of SRNS", the relocation execution trigger may be 
received either from the Uu interface or as an implementation option from the lur interface. If the type of relocation of 
SRNS is "UE not involved in relocation of SRNS", the relocation execution trigger is received from the lur interface. 

When RELOCATION DETECT message is sent, the target RNC shall start SRNC operation. 

Upon reception of RELOCATION DETECT message, the CN may switch the user plane from the source RNC to the 
target RNC. 

8.8.3 Abnormal Conditions 

Interactions with Relocation Complete procedure: 

If the RELOCATION COMPLETE message is received by CN before the reception of RELOCATION DETECT 
message, the CN shall handle the RELOCATION COMPLETE message normally. 

8.8.4 Co-ordination of Two lu Signalling Connections 

When Relocation Detect procedure is to be initiated by the target RNC, the target RNC shall initiate the Relocation 
Detect procedure on all lu signalling connections existing for the UE between the target RNC and the CN. 

8.9 Relocation Complete 
8.9.1 General 

The purpose of Relocation Complete procedure is to indicate by the target RNC the completion of relocation of SRNS 
to the CN. Procedure shall be co-ordinated in all lu signalling connections existing for the UE. The procedure uses 
connection oriented signalling. 



£75/ 



3GPP TS 25.41 3 version 4.1 0.0 Release 4 36 ETSI TS 1 25 41 3 V4.1 0.0 (2003-09) 

8.9.2 Successful Operation 



Target RNC CN 

RELOCATION COMPLETE 

Figure 10: Relocation Complete procedure. Successful operation. 

When the new SRNC-ID and serving RNC Radio Network Temporary Identity are successfully exchanged with the UE 
by the radio protocols, target RNC shall initiate Relocation Complete procedure by sending RELOCATION 
COMPLETE message to CN. Upon reception of the RELOCATION COMPLETE message by the CN, the CN should 
then stop the TRELoccompiete timer. 

8.9.3 Abnormal Conditions 

If the timer TRELoccompiete expires: 

The CN should initiate release of lu connections towards the source and the target RNC by initiating the lu 
Release procedure with an appropriate value for the Cause IE, e.g. "TRELoccompiete expiry". 

Interactions with the Relocation Detect procedure: 

If the RELOCATION DETECT message is not received by CN before reception of RELOCATION COMPLETE 
message, CN shall handle the RELOCATION COMPLETE message normally. 

8.9.4 Co-ordination of Two lu Signalling Connections 

When Relocation Complete procedure is to be initiated by target RNC, target RNC shall initiate the Relocation 
Complete procedure on all lu signalling connections existing for the UE between target RNC and CN. 

8.10 Relocation Cancel 
8.10.1 General 

The purpose of the Relocation Cancel procedure is to enable source RNC to cancel an ongoing relocation of SRNS. The 
Relocation Cancel procedure may be initiated by the source RNC during and after the Relocation Preparation procedure 
if either of the following conditions is fulfilled: 

1. Source RNC has not yet initiated the execution of relocation of SRNS, neither via the lur interface nor via the Uu 
interface. 

2. After having initiated the execution of relocation of SRNS the UE has returned to source RNC by transmitting an 
RRC message which indicates that the UE considers the source RNC as its serving RNC. 

The procedure shall be co-ordinated in all lu signalling connections for which the Relocation Preparation procedure has 
been initiated. The procedure uses connection oriented signalling. 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



37 



ETSI TS 125 413 V4.10.0 (2003-09) 



8.10.2 Successful Operation 



Source RNC 



CN 



RELOCATION CANCEL 



RELOCATION CANCEL 
ACKNOWLEDGE 



Figure 11: Relocation Cancel procedure. Successful operation. 

RNC shall initiate the procedure by sending RELOCATION CANCEL message to CN. This message shall indicate the 
reason for cancelling the relocation of SRNS by appropriate value of the Cause IE. Upon reception of RELOCATION 
CANCEL message, CN shall send RELOCATION CANCEL ACKNOWLEDGE message to source RNC. 

Transmission and reception of RELOCATION CANCEL ACKNOWLEDGE message terminates the procedure in CN 
and source RNC respectively. After this, the source RNC does not have a prepared relocation for that lu signalling 
connection. 

Interactions with Relocation Preparation procedure: 

Upon reception of RELOCATION CANCEL message from source RNC, CN shall locally terminate the possibly 
ongoing Relocation Preparation procedure towards that RNC and abandon the relocation of SRNS. 

If source RNC receives RELOCATION COMMAND message from CN after Relocation Cancel procedure is initiated, 
source RNC shall ignore the received RELOCATION COMMAND message. 

8.10.3 Unsuccessful Operation 

Not applicable. 

8.10.4 Abnormal Conditions 

Not applicable. 

8.1 0.5 Co-ordination of Two lu Signalling Connections 

If Relocation Cancel procedure is to be initiated due to other reasons than reception of RELOCATION 
PREPARATION FAILURE message. Relocation Cancel procedure shall be initiated on all lu signalling connections 
existing for the UE in which the Relocation Preparation procedure has not terminated unsuccessfully. 

8.1 1 SRNS Context Transfer 
8.11.1 General 

The purpose of the SRNS Context Transfer procedure is to trigger the transfer of SRNS contexts from the source RNC 
to the CN (PS domain) in case of intersystem change or in some further cases described in [21]. The procedure uses 
connection oriented signalling. 



£75/ 



3GPP TS 25.41 3 version 4.1 0.0 Release 4 38 ETSI TS 1 25 41 3 V4.1 0.0 (2003-09) 

8. 11 .2 Successful Operation 



RNC 



CN 



SRNS CONTEXT REQUEST 

-^ 

SRNS CONTEXT RESPONSE 

►J 



Figure 12: SRNS Context Transfer procedure. Successful operation. 

The CN shall initiate the procedure by sending a SRNS CONTEXT REQUEST message to the source RNC. The SRNS 
CONTEXT REQUEST message shall include the list of RABs whose contexts should be transferred. 

The source RNC shall respond to the CN with a SRNS CONTEXT RESPONSE message containing all the referenced 
RABs including both, successful and unsuccessful RABs transfers. For each RAB whose transfer is successful, the 
following context information elements shall be included: 

- RAB ID; 

always when available, the sequence number for the next downlink GTP-PDU to be sent to the UE i.e. DL GTP- 
PDU Sequence Number; 

always when available, the sequence number for the next uplink GTP-PDU to be tunnelled to the GGSN i.e. UL 
GTP-PDU Sequence Number; 

always when available, the radio interface sequence number (PDCP) [17] of the next downlink N-PDU (PDCP 
SDU) that would have been sent to the UE by a source system i.e. DL N-PDU Sequence Number IE; 

always when available, the radio interface sequence number (PDCP) [17] of the next uplink N-PDU (PDCP 
SDU) that would have been expected from the UE by a source system i.e. UL N-PDU Sequence Number IE. 

Transmission and reception of the SRNS CONTEXT RESPONSE message shall terminate the procedure in the 
UTRAN and the CN respectively. 

8.1 1 .3 Unsuccessful Operation 

For each RAB for which UTRAN is not able to transfer the RAB context, e.g. if the RAB ID is unknown to the RNC, 
this RAB ID is included in the SRNS CONTEXT RESPONSE message together with a Cause IE, e.g. "Invalid RAB 
ID". 

8.1 1 .4 Abnormal Conditions 

Not applicable. 

8.12 SRNS Data Forwarding Initiation 
8.12.1 General 

The purpose of the SRNS Data Forwarding procedure is to trigger the transfer of N-PDUs from the RNC to the CN 
(PS domain) in case of intersystem change or in some further cases described in [21]. The procedure uses connection 
oriented signalling. 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



39 



ETSI TS 125 413 V4.10.0 (2003-09) 



8.12.2 Successful Operation 



RNC 



CN 



SRNS DATA FORWARD COMMAND 



Figure 13: SRNS Data Forwarding Initiation procedure. Successful operation. 

CN initiates the procedure by sending SRNS DATA FORWARD COMMAND message to UTRAN. SRNS DATA 
FORWARD COMMAND message includes the list of RABs towards the PS domain whose data should be forwarded 
and the necessary information for establishing a GTP tunnel to be used for data forwarding. For each RAB indicated the 
list shall include the RAB ID IE, the Transport Layer Address IE and the lu Transport Association IE. 

Upon reception of SRNS DATA FORWARD COMMAND message RNC starts the timer ToATAfwd- 

8.12.3 Abnormal Conditions 

Not applicable. 

8.13 SRNS Context Forwarding from Source RNC to CN 

8.13.1 General 

The purpose of this procedure is to transfer SRNS contexts from the source RNC to the CN (PS domain) in case of 
handover via the CN. The procedure uses connection oriented signalling. SRNS contexts are sent for each concerned 
RAB among those that are supported by the target system, and for which at least either GTP-PDU or PDCP sequence 
numbering is available. The contexts contain the sequence numbers of the GTP-PDUs next to be transmitted in the 
uplink and downlink directions, if available, and the next PDCP sequence numbers that would have been used to send 
and receive data from the UE, if available. 

8.13.2 Successful Operation 



Source RNC 



CN 



FORWARD SRNS CONTEXT 



Figure 14: SRNS Context forwarding from source RNC to CN. Successful operation. 

The source RNC initialises the procedure by sending FORWARD SRNS CONTEXT message to the CN. The 
FORWARD SRNS CONTEXT message contains the RAB Context information for each referenced RAB. For each 
RAB the following information shall be included: 

- RAB ID 

always when available, the sequence number for the next downlink GTP-PDU to be sent to the UE, and 
always when available, the sequence number for the next uplink GTP-PDU to be tunnelled to the GGSN; 



£75/ 



3GPP TS 25.41 3 version 4.1 0.0 Release 4 40 ETSI TS 1 25 41 3 V4.1 0.0 (2003-09) 

always when available, the radio interface sequence number (PDCP) [17] of the next uplink N-PDU (PDCP 
SDU) that would have been expected from the UE by a source system i.e. UL N-PDU Sequence Number IE; 

always when available, the radio interface sequence number (PDCP) [17] of the next downlink N-PDU (PDCP 
SDU) that would have been sent to the UE by a source system i.e. DL N-PDU Sequence Number IE. 

8.13.3 Abnormal Conditions 

Not applicable. 

8.14 SRNS Context Forwarding to Target RNC from CN 
8.14.1 General 

The purpose of this procedure is to transfer SRNS contexts from the CN (PS domain) to the target RNC in case of 
handover via the CN. The procedure uses connection oriented signalling. SRNS contexts are sent for each referenced 
RAB, for which at least either GTP-PDU or PDCP sequence numbering is available. The contexts contain the sequence 
numbers of the GTP-PDUs next to be transmitted in the uplink and downlink directions, if available, and the next PDCP 
sequence numbers that would have been used to send and receive data from the UE, if available. 



8.14.2 Successful Operation 



Target RNC 



FORWARD SRNS CONTEXT 
< 



CN 



Figure 15: SRNS Context forwarding to target RNC from CN. Successful operation. 

The CN initialises the procedure by sending FORWARD SRNS CONTEXT message to the target RNC. The 
FORWARD SRNS CONTEXT message contains the RAB Context information for each referenced RAB. For each 
RAB the following information shall be included: 

- RAB ID 

always when available, the sequence number for the next downlink GTP-PDU to be sent to the UE, and 

always when available, the sequence number for the next uplink GTP-PDU to be tunnelled to the GGSN; 

always when available, the radio interface sequence number (PDCP) [17] of the next uplink N-PDU (PDCP 
SDU) that would have been expected from the UE by a source system i.e. UL N-PDU Sequence Number IE; 

always when available, the radio interface sequence number (PDCP) [17] of the next downlink N-PDU (PDCP 
SDU) that would have been sent to the UE by a source system i.e. DL N-PDU Sequence Number IE. 

8.14.3 Abnormal Conditions 

Not applicable. 



£75/ 



3GPP TS 25.41 3 version 4.1 0.0 Release 4 41 ETSI TS 1 25 41 3 V4.1 0.0 (2003-09) 

8.15 Paging 

8.15.1 General 

The purpose of the Paging procedure is to enable the CN to request the UTRAN to contact that UE. The procedure uses 
connectionless signalling. 

8.15.2 Successful Operation 



RNC 



CN 



PAGING 

M 



Figure 16: Paging procedure. Successful operation. 

The CN shall initiate the procedure by sending a PAGING message. The PAGING message shall contain following lEs: 

CN Domain Indicator. 

Permanent NAS UE Identity. 

DRX Cycle Length Coefficient (if available). 
The PAGING message may contain following IBs: 

Temporary UE Identity. 

Paging Area. 

Paging Cause. 

Non Searching Indicator. 

The CN Domain Indicator IE shall be used by the RNC to identify from which CN domain the paging request 
originates. 

The Permanent NAS UE Identity IE (i.e. IMSI) shall be used by the UTRAN paging co-ordination function to check if a 
signalling connection towards the other CN domain already exists for this UE. In that case, the radio interface paging 
message shall be sent via that connection instead of using the paging broadcast channel. 

The Temporary UE Identity IE (e.g. TMSI) is the temporary identity of the user (allocated by that CN Domain) which 
can be used in a radio interface paging message. If the Temporary UE Identity IE is not included in the PAGING 
message, the RNC shall use the Permanent NAS UE Identity instead - if no signalling connection exists. 

The Paging Area IE shall be used by the RNC to identify the area in which the radio interface paging message shall be 
broadcast in case no signalling connection, as described above, already exists for the UE. If the Paging Area IE is not 
included in the PAGING message, the whole RNC area shall be used as Paging Area - if no signalling connection exists 
for that UE. 

The Paging Cause IE shall indicate to the RNC the reason for sending the PAGING message. The paging cause is 
transferred transparently to the UE. 

The Non Searching Indication IE shall, if present, be used by the RNC to decide whether the UTRAN paging co- 
ordination function needs to be activated or not. In the absence of this IE, UTRAN paging co-ordination shall be 
performed. 

The DRX Cycle Length Coefficient IE may be included in the PAGING message, and if present, the UTRAN shall, 
when applicable, use it for calculating the paging occasions for the UE. 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



42 



ETSI TS 125 413 V4.10.0 (2003-09) 



It should be noted that each PAGING message on the lu interface relates to only one UE and therefore the RNC has to 
pack the pages into the relevant radio interface paging message. 

The core network is responsible for the paging repetition over the lu interface. 

8.15.3 Abnormal Conditions 

Not applicable. 

8.16 Common ID 
8.16.1 General 

The purpose of the Common ID procedure is to inform the RNC about the permanent N AS UE Identity (i.e. IMSI) of a 
user. This is used by the RNC e.g. to create a reference between the permanent NAS UE identity of the user and the 
RRC connection of that user for UTRAN paging co-ordination. The procedure uses connection oriented signalling. 



8.16.2 Successful Operation 

RNC 



CN 



COMMON ID 



Figure 17: Common ID procedure. Successful operation. 

After having established an lu signalling connection, and if the Permanent NAS UE identity (i.e. IMSI) is available, the 
CN shall send a COMMON ID message, containing the Permanent NAS UE Identity IE to the RNC. The RNC shall 
associate the permanent identity to the RRC Connection of that user and shall save it for the duration of the RRC 
connection. 

8.16.3 Abnormal Conditions 

Not applicable. 

8.17 CN Invoke Trace 

8.17.1 General 

The purpose of the CN Invoke Trace procedure is to inform the RNC that it should begin producing a trace record of a 
type indicated by the CN and related to the UE. The procedure uses connection oriented signalling. 

8.17.2 Successful Operation 



RNC 



CN 



CN INVOKE TRACE 



Figure 18: CN Invoke Trace procedure. Successful operation. 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



43 



ETSI TS 125 413 V4.10.0 (2003-09) 



The CN Invoke Trace procedure is invoked by the CN by sending a CN INVOKE TRACE message to the RNC. 

The CN INVOKE TRACE message shall include the Trace Type IE to indicate the events and parameters to be 
recorded. 

The message shall include a Trace Reference IE which is allocated by the entity which triggered the trace. 

The message may include the OMC ID IE, which if present, indicates the OMC to which the record is destined. 

The message may include the UE Identity IE, which if present, indicates the UE to which this record pertains to. 

The message may include the Trigger ID IE, which if present, indicates the entity which triggered the trace. 

The Trace Reference and Trigger ID lEs are used to tag the trace record to allow simpler construction of the total record 
by the entity which combines trace records. 

Interaction with Relocation: 



The order to perform tracing is lost in UTRAN at successful Relocation of SRNS. If the tracing shall continue also after 
the relocation has been performed, the CN Invoke Trace procedure shall thus be re-initiated from the CN towards the 
future SRNC after the Relocation Resource Allocation procedure has been executed successfully. 

8.17.3 Abnormal Conditions 

Not apphcable. 

8.18 Security Mode Control 

8.18.1 General 

The purpose of the Security Mode Control procedure is to allow the CN to pass cipher and integrity mode information 
to the UTRAN. UTRAN uses this information to select and load the encryption device for user and signalling data with 
the appropriate parameters, and also to store the appropriate parameters for the integrity algorithm. The procedure uses 
connection oriented signalling. 

8.18.2 Successful Operation 



RNC 



CN 



SECURITY MODE 
COMMAND 



SECURITY MODE 
COMPLETE 



Figure 19: Security IVIode Control procedure. Successful operation. 

The CN shall start the procedure by sending to the UTRAN a SECURITY MODE COMMAND message. This message 
may contain the Encryption Information IE and shall contain the Integrity Protection Information IE, specifying, in 
preferred order with the most preferred first in the list, which ciphering, if any, and integrity protection algorithms may 
be used by the UTRAN. 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



44 



ETSI TS 125 413 V4.10.0 (2003-09) 



The Permitted Encryption Algorithms IE within the Encryption Information IE may contain "no encryption" within an 
element of its Hst in order to allow the RNC not to cipher the respective connection. This can be done either by not 
starting ciphering or by using the UEAO algorithm. In the absence of the Encryption Information group IE in 
SECURITY MODE COMMAND message, the RNC shall not start ciphering. 

Upon reception of the SECURITY MODE COMMAND message, the UTRAN shall internally select appropriate 
algorithms, taking into account the UE/UTRAN capabilities. If a signalling connection already exists towards the other 
core network domain, and integrity protection and ciphering information has been received from that core network 
domain, the same algorithm(s) as being used for that core network domain shall be selected. This also means for 
encryption that if "no encryption" or no Encryption Information IE has been received from the first core network 
domain and ciphering has not been started, ciphering shall also not be started for the second core network domain. The 
UTRAN shall then trigger the execution of the corresponding radio interface procedure and, if applicable, start/restart 
the encryption device and also start/restart the integrity protection. 

The CN may send a SECURITY MODE COMMAND message towards the RNC also when integrity protection and 
possibly ciphering has already been started for an existing signalling connection towards that core network domain. 
This may be used to activate new integrity protection and ciphering keys. The included integrity protection and 
ciphering information shall then support (at least) the integrity protection alternative and the ciphering alternative 
presently being used and the Key Status IE shall have the value "New". 

When the execution of the radio interface procedure is successfully finished, UTRAN shall return a SECURITY MODE 
COMPLETE message to the CN. This message shall include the Chosen Integrity Protection Algorithm IE and may 
include the Chosen Encryption Algorithm IE. 

The Chosen Encryption Algorithm IE shall be included in the SECURITY MODE COMPLETE message if, and only if 
the Encryption Information IE was included in the SECURITY MODE COMMAND message. 

The set of permitted algorithms specified in the SECURITY MODE COMMAND message shall remain applicable for 
subsequent RAB Assignments and Intra-UTRAN Relocations. 

In case of a UE with Radio Access Bearers towards both core networks, the user data towards CS shall always be 
ciphered with the ciphering key received from CS and the user data towards PS with the ciphering key received from 
PS. The signalling data shall always be ciphered with the last received ciphering key and integrity protected with the 
last received integrity protection key from any of the two CNs. 



8.18.3 Unsuccessful Operation 



RNC 



CN 



SECURITY MODE 
COMMAND 



SECURITY MODE 
REJECT 



Figure 20: Security IVIode Control procedure. Unsuccessful operation. 

If the UTRAN or the UE is unable to support the ciphering and/or integrity protection algorithms specified in the 
SECURITY MODE COMMAND message, then the UTRAN shall return to CN a SECURITY MODE REJECT 
message with cause value "Requested Ciphering and/or Integrity Protection Algorithms not Supported". If the radio 
interface Security Control procedure fails, a SECURITY MODE REJECT message shall be sent to CN with cause value 
"Failure in the Radio Interface Procedure". 



£75/ 



3GPP TS 25.41 3 version 4.1 0.0 Release 4 45 ETSI TS 1 25 41 3 V4.1 0.0 (2003-09) 

8.18.4 Abnormal Conditions 

If, when establishing a signalHng connection towards a second core network domain, the integrity protection and 
ciphering information specified in the SECURITY MODE COMMAND message does not support the integrity 
protection alternative and the ciphering alternative presently being used, a SECURITY MODE REJECT message shall 
be sent to the second core network domain with cause value "Conflict with already existing Integrity protection and/or 
Ciphering information". 

If, upon reception of a SECURITY MODE COMMAND message from a core network domain with an already existing 
signalling connection from that core nework domain and for which integrity protection and possibly ciphering has 
already been started, the Key Status IE has the value "Old", a SECURITY MODE REJECT message shall be returned 
with cause value "Conflict with already existing Integrity protection and/or Ciphering information". 

If, upon reception of a SECURITY MODE COMMAND message from a core network domain with an already existing 
signalling connection and for which integrity protection and possibly ciphering has already been started, the included 
integrity protection and ciphering information does not support the integrity protection alternative and the ciphering 
alternative presently being used, a SECURITY MODE REJECT message shall be returned with cause value "Conflict 
with already existing Integrity protection and/or Ciphering information". 

8.19 Location Reporting Control 
8.19.1 General 

The purpose of the Location Reporting Control procedure is to allow the CN to request information on the location of a 
given UE. The procedure uses connection oriented signalling. 



8.19.2 Successful Operation 



RNC 



CN 



LOCATION REPORTING 

CONTROL 

< 



Figure 21 : Location Reporting Control procedure. Successful operation. 

The CN shall initiate the procedure by generating a LOCATION REPORTING CONTROL message. 
The Request Type IE shall indicate to the serving RNC whether: 

to report directly; 

to stop a direct report; 

to report upon change of Service area, or 

to stop reporting at change of Service Area. 

If reporting upon change of Service Area is requested, the Serving RNC shall report whenever the UE moves between 
Service Areas. For this procedure, only Service Areas that are defined for the PS and CS domains shall be considered. 

The Request Type IE shall also indicate what type of location information the serving RNC shall report. The location 
information is either of the following types: 

Service Area Identifier, or 

Geographical area, including geographical coordinates with or without requested accuracy. If the Vertical 
Accuracy Code IE is included, the Accuracy Code IE in the Request Type IE shall be present. The Accuracy 
Code IE shall be understood as the horizontal accuracy code. 



£75/ 



3GPP TS 25.41 3 version 4.1 0.0 Release 4 46 ETSI TS 1 25 41 3 V4.1 0.0 (2003-09) 

A request for a direct report can be done in parallel with having an active request to report upon change of Service Area 
for the same UE. The request to report upon change of Service Area shall not be affected by this. 

Any of the Vertical Accuracy Code IE, Response Time IE, Positioning Priority IE or Client Type IE shall be included 
according to the following rules: 

Vertical Accuracy Code shall be included, if available, in connection with Geographical Area, 

Response time shall be included, if available, in connection with request for start of direct reporting of 
Geographical Area, 

Client type shall be included in connection with request for start of direct reporting of Geographical Area and, if 
available, in request for direct reporting of SAI, 

Positioning Priority shall be included, if available, in connection with request for start of direct reporting or in 
connection with request for start of reporting upon change of Service Area. 

When no Positioning Priority IE is included, the RNC shall consider the request as if "Normal Priority" value had been 
received. 

When no Response Time IE is included, the RNC shall consider the request as if "Delay Tolerant" value had been 
received. 

Interaction with Relocation: 

The order to perform location reporting at change of Service Area is lost in UTRAN at successful Relocation of SRNS. 
If the location reporting at change of Service Area shall continue also after the relocation has been performed, the 
Location Reporting Control procedure shall thus be re-initiated from the CN towards the future SRNC after the 
Relocation Resource Allocation procedure has been executed successfully. 

8.19.3 Abnormal Conditions 

Not apphcable. 

8.20 Location Report 
8.20.1 General 

The purpose of the Location Report procedure is to provide the UE's location information to the CN. The procedure 
uses connection oriented signalling. 



8.20.2 Successful Operation 



RNC 



CN 



LOCATION REPORT ^ 



Figure 22: Location Report procedure. Successful operation. 

The serving RNC shall initiate the procedure by generating a LOCATION REPORT message. The LOCATION 
REPORT message may be used as a response for the LOCATION REPORTING CONTROL message. Also, when a 
user enters or leaves a classified zone set by O&M, e.g. zone where a disaster occurred, a LOCATION REPORT 
message shall be sent to the CN including the Service Area of the UE in the Area Identity IE. The Cause IE shall 
indicate the appropriate cause value to CN, e.g. "User Restriction Start Indication" and "User Restriction End 
Indication". The CN shall react to the LOCATION REPORT message with CN vendor specific actions. 



£75/ 



3GPP TS 25.41 3 version 4.1 0.0 Release 4 47 ETSI TS 1 25 41 3 V4.1 0.0 (2003-09) 

For this procedure, only Service Areas that are defined for the PS and CS domains shall be considered. 

In case reporting at change of Service Area is requested by the CN, then the RNC shall issue a LOCATION REPORT 

message. 

- whenever the information given in the previous LOCATION REPORT message or INITIAL UE MESSAGE 
message is not anymore valid. 

- upon receipt of the first LOCATION REPORTING CONTROL message following a Relocation Resource 
Allocation procedure, with the Event IE included in the Request Type IE set to "Change of Service Area", as soon 
as SAI becomes available in the new SRNC and the relocation procedure has been successfully completed. 

In the case when Service Area is reported, the RNC shall include to the LOCATION REPORT message in the Area 
Identity IE the Service Area, which includes at least one of the cells from which the UE is consuming radio resources. 

In the case when the LOCATION REPORT message is sent as an answer to a request for a direct report or at a change 
of Service Area, the Request Type IE from the LOCATION REPORTING CONTROL message shall be included. 

If the LOCATION REPORT message is sent as an answer to a request for a direct report of Service Area and the 
current Service Area can not be determined by the RNC, then the Area Identity IE shall be omitted and a cause value 
shall be included to indicate that the request could not be fulfilled, e.g. "Requested Information Not Available" or 
"Location Reporting Congestion". The RNC may also include the Last Known Service Area IE. 

If the RNC can not deliver the location information as requested by the CN, due to either the non-support of the 
requested event or the non-support of the requested report area or if RNC is currently not able to reach the UE, the RNC 
shall indicate the UE location to be "Undetermined" by omitting the Area Identity IE. A cause value shall instead be 
added to indicate the reason for the undetermined location, e.g. "Requested Request Type not supported" or "Location 
Reporting Congestion" or "No Resource Available". 

If the Location Report procedure was triggered by a LOCATION REPORTING CONTROL message, which included a 
request to report a geographical area with a specific accuracy, the LOCATION REPORT message shall include the 
Geographical Area IE within the Area Identity IE containing either a point with indicated uncertainty or a polygon or an 
other type, which fulfils the requested accuracy as accurately as possible. If, on the other hand, no specific accuracy 
level was requested in the LOCATION REPORTING CONTROL message, the LOCATION REPORT message shall 
include the Geographical Area IE within the. Area Identity IE, the reported Geographical Area IE may include an 
accuracy. 

8.20.3 Abnormal Conditions 

Not applicable. 

8.21 Data Volume Report 
8.21.1 General 

The Data Volume Report procedure is used by CN to request the unsuccessfully transmitted DL data volume for 
specific RABs. This procedure only applies to PS domain. The procedure uses connection oriented signalling. 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



48 



ETSI TS 125 413 V4.10.0 (2003-09) 



8.21.2 Successful Operation 



RNC 



CN 



DATA VOLUME REPORT REOUEST 



DATA VOLUME REPORT 



Figure 23: Data Volume Report procedure. Successful operation. 

The procedure is initiated by CN by sending DATA VOLUME REPORT REQUEST message to UTRAN. This 
message shall contain the list of RAB ID lEs to identify the RABs for which the unsuccessfully transmitted DL data 
volume shall be reported. 

At reception of DATA VOLUME REPORT REQUEST message UTRAN shall produce the DATA VOLUME 
REPORT message. This message shall include for each RAB successfully addressed within the RAB Data Volume 
Report List IE the amount of unsuccessfully transmitted DL data in the Unsuccessfully Transmitted DL Data Volume IE 
since the last data volume indication to CN and may contain the Data Volume Reference IE. 

The message may contain for each RAB successfully addressed a maximum of two RAB Data Volume Report Item lEs 
within the RAB Data Volume Report List IE for the case when there is a need to report two different data volumes since 
the last data volume indication to CN. UTRAN shall also reset the data volume counter for the reported RABs. UTRAN 
shall send the DATA VOLUME REPORT message to CN. Transmission and reception of DATA VOLUME REPORT 
message terminates the procedure in UTRAN and CN respectively. 

The Data Volume Reference IE, if included, indicates the time when the data volume is counted. 

8.21.3 Unsuccessful Operation 

The RAB ID IE for each RAB for which UTRAN is not able to transfer a data volume report is included in the DATA 
VOLUME REPORT message together with a Cause IE, e.g. "Invalid RAB ID". 

8.21.4 Abnormal Conditions 

Not applicable. 

8.22 Initial UE Message 
8.22.1 General 

The purpose of the Initial UE Message procedure is to establish an lu signalling connection between a CN domain and 
the RNC and to transfer the initial NAS-PDU to the default CN node. The procedure uses connection oriented 
signalling. 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



49 



ETSI TS 125 413 V4.10.0 (2003-09) 



8.22.2 Successful Operation 



RNC 



CN 



INITIAL UE MESSAGE 



Figure 24: Initial UE Message procedure. Successful operation. 

When RNC has received from radio interface a NAS message (see [8]) to be forwarded to CN domain to which the lu 
signalHng connection for the UE does not exist, RNC shall initiate the Initial UE Message procedure and send the 
INITIAL UE MESSAGE message to the CN. 

In addition to the received NAS-PDU, RNC shall add following information to the INITIAL UE MESSAGE message: 

CN domain indicator, indicating the CN domain towards which this message is sent. 

For CS domain, the LAI which was the last LAI indicated to the UE by UTRAN via the current RRC 
connection, or if UTRAN had not yet indicated any LAI to the UE via the current RRC connection, then the LAI 
of the cell via which the current RRC connection was established. 

- For PS domain, the LAI+RAC which were the last LAI+RAC indicated to the UE by UTRAN via the current 
RRC connection, or if UTRAN had not yet indicated any LAI+RAC to the UE via the current RRC connection, 
then the LAI+RAC of the cell via which the current RRC connection was established. 

Service Area corresponding to at least one of the cells from which the UE is consuming radio resources. 

lu signalling connection identifier. 

- Global RNC identifier. 

The lu Signalling Connection Identifier IE contains an lu signalling connection identifier which is allocated by the 
RNC. The value for the lu Signalling Connection Identifier IE shall be allocated so as to uniquely identify an lu 
signalling connection for the RNC. The CN should store and remember this identifier for the duration of the lu 
connection. 

Whereas several processing entities within the CN (e.g. charging, interception, etc.) may make use of the location 
information given in the SAI IE and the LAI (and RAC) IE, the mobility management within the CN shall rely on the 
information given within the LAI IE (resp. LAI and RAC lEs) only. 

8.23 Direct Transfer 
8.23.1 General 

The purpose of the Direct Transfer procedure is to carry UE - CN signalling messages over the lu Interface. The 
UE - CN signalling messages are not interpreted by the UTRAN, and their content (e.g. MM or CC message) is outside 
the scope of this specification (see [8]). The UE - CN signalling messages are transported as a parameter in the 
DIRECT TRANSFER messages. The procedure uses connection oriented signalling. 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



50 



ETSI TS 125 413 V4.10.0 (2003-09) 



8.23.2 Successful Operation 
8.23.2.1 CN Originated Direct Transfer 



RNC 



CN 



DIRECT TRANSFER 



Figure 25: Direct Transfer, CN originated. Successful operation. 

If a UE - CN signalling message has to be sent from the CN to the UE, the CN shall send a DIRECT TRANSFER 
message to the RNC including the UE - CN signalling message as a NAS-PDU IE. 

If the DIRECT TRANSFER message is sent in the downlink direction it shall include the SAPI IE and shall not include 
the LAI + RAC IE and the SAI IE. The use of the SAPI IE included in the DIRECT TRANSFER message enables the 
UTRAN to provide specific service for the transport of the messages. 

8.23.2.2 UTRAN Originated Direct Transfer 

RNC CN 



DIRECT TRANSFER 



Figure 26: Direct Transfer, RNC originated. Successful operation. 

If a UE - CN signalling message has to be sent from the RNC to the CN without interpretation, the RNC shall send a 
DIRECT TRANSFER message to the CN including the UE - CN signalHng message as a NAS-PDU IE. 

If the DIRECT TRANSFER message shall be sent to the PS domain, RNC shall also add the LAI and the RAC lEs, 
which were the last LAI + RAC indicated to the UE by UTRAN via the current RRC connection, or if UTRAN had not 
yet indicated any LAI + RAC to the UE via the current RRC connection, then the LAI + RAC of the cell via which the 
current RRC connection was established. If the DIRECT TRANSFER message is sent to the PS domain, the RNC shall 
also add Service Area corresponding to at least one of the cells from which the UE is consuming radio resources. If the 
DIRECT TRANSFER message is sent in uplink direction the RNC shall not include the SAPI IE. 

8.23.3 Abnormal Conditions 

If the DIRECT TRANSFER message is sent by the RNC to the PS domain, and is missing any of the LAI IE, RAC IE, 
SAI IE, the CN shall continue with the Direct Transfer procedure, ignoring the missing IE. 

If the DIRECT TRANSFER message is sent by the CN to the RNC without the SAPI IE, the RNC shall continue with 
the Direct Transfer procedure. 

8.24 Void 



£75/ 



3GPP TS 25.41 3 version 4.1 0.0 Release 4 51 ETSI TS 1 25 41 3 V4.1 0.0 (2003-09) 

8.25 Overload Control 

8.25.1 General 

This procedure is defined to give some degree of signalling flow control. At the UTRAN "Processor Overload" and 
"Overload in the Capability to Send Signalling Messages to the UE" are catered for, and at the CN "Processor 
Overload" is catered for. The procedure uses connectionless signalling. 

The philosophy used is to stem the traffic at source with known effect on the service. The algorithm used is: 

At the CN side: 

If Tjgoc is not running and an OVERLOAD message or "Signalling Point Congested" information is received, 
the traffic should be reduced by one step. It is also possible, optionally, to indicate the number of steps to reduce 
the traffic within the Number of Steps IE. At the same time, timers Tigoc and Ti^xc should be started. 

- During Tigoc all received OVERLOAD messages or "SignalUng Point Congested" information should be 
ignored. 

This step by step reduction of traffic should be continued until maximum reduction is obtained by arriving at the 
last step. 

If Ti„xc expires (i.e. no OVERLOAD message or "Signalling Point Congested" information is received during 
Tinxc) the traffic should be increased by one step and Ti^xc should be started unless normal load has been 
resumed. 

At the UTRAN side: 

If TigOR is not running and an OVERLOAD message or "Signalling Point Congested" information is received, 
the traffic should be reduced by one step. It is also possible, optionally, to indicate the number of steps to reduce 
the traffic within the Number of Steps IE. At the same time, timers TjgOR and TjnXR should be started. 

During TigOR all received OVERLOAD messages or "Signalling Point Congested" information should be 
ignored. 

This step-by-step reduction of traffic should be continued until maximum reduction is obtained by arriving at the 
last step. 

If TinXR expires (i.e. no OVERLOAD message or "Signalling Point Congested" information is received during 
TinTR) the traffic should be increased by one step and TjnXR should be started unless normal load has been 
resumed. 

The number of steps and the method of reducing the load are considered to be an implementation specific function. 

There may be other traffic control mechanisms from O&M activities occurring simultaneously. 

8.25.2 Philosophy 

Void. 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



52 



ETSI TS 125 413 V4.10.0 (2003-09) 



8.25.3 Successful Operation 
8.25.3.1 Overload at the CN 



RNC 



CN 



OVERLOAD 



Figure 27: Overload at the CN. Successful operation. 

The CN should indicate to the RNC that it is in a congested state by sending an OVERLOAD message. The CN Domain 
Indicator IE may be included, if the CN can determine the domain suffering the signalling traffic overload. A specific 
CN node shall send this message only towards those RNCs for which it is default CN node. 

The UTRAN receipt of this message should cause the reduction of signalling traffic towards the CN. If CN Domain 
Indicator IE is indicated within the OVERLOAD message, the RNC should apply signalling traffic reduction 
mechanisms to the indicated domain. 



8.25.3.2 



Overload at the UTRAN 



RNC 



CN 



OVERLOAD 



Figure 28: Overload at the UTRAN. Successful operation. 

If the UTRAN is not capable to send signalling messages to the UE due to overloaded resources then the UTRAN 
should send an OVERLOAD message to the CN. The RNC shall include the Global RNC-ID IE in this message. A 
specific RNC shall send this message only towards its default CN node of the concerned domain(s). 

8.25.4 Abnormal Conditions 

Not applicable. 

8.26 Reset 
8.26.1 General 

The purpose of the Reset procedure is to initialise the UTRAN in the event of a failure in the CN or vice versa. The 
procedure uses connectionless signalling. 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



53 



ETSI TS 125 413 V4.10.0 (2003-09) 



8.26.2 Successful Operation 

8.26.2.1 Reset Procedure Initiated from the CN 



RNC 



CN 



RESET 



RESET ACKNOWLEDGE. 



Figure 29: Reset procedure initiated from the CN. Successful operation. 

In the event of a failure at the CN, which has resuhed in the loss of transaction reference information, a RESET 
message shall be sent to the RNC. When a CN node sends this message towards an RNC for which it is not the default 
CN node, the Global CN-ID IE shall be included. This message is used by the UTRAN to release affected Radio Access 
Bearers and to erase all affected references for the specific CN node that sent the RESET message, i.e. the CN node 
indicated by the Global CN-ID IE or, if this IE is not included, the default CN node for the indicated CN domain. 

After a guard period of TR^tc seconds a RESET ACKNOWLEDGE message shall be returned to the CN, indicating that 
all UEs which were involved in a call are no longer transmitting and that all references at the UTRAN have been 
cleared. 

The RNC shall include the Global RNC-ID IE in the RESET ACKNOWLEDGE message. The Global RNC-ID IE shall 
not be included in the RESET message. 

Interactions with other procedures: 

In case of interactions with other procedures, the Reset procedure shall always override all other procedures. 



8.26.2.2 



Reset Procedure Initiated from the UTRAN 



RNC 



CN 



RESET 



.RESET ACKNOWLEDGE 



Figure 30: Reset procedure initiated from the UTRAN. Successful operation. 



£75/ 



3GPP TS 25.41 3 version 4.1 0.0 Release 4 54 ETSI TS 1 25 41 3 V4.1 0.0 (2003-09) 

In the event of a failure at the UTRAN which has resuhed in the loss of transaction reference information, a RESET 
message shall be sent to all CN nodes towards which the RNC has lu signalling connections established. This message 
is used by the CN to release affected Radio Access Bearers and to erase all affected references for the sending RNC. 

The RNC shall include the Global RNC-ID IE in the RESET message. 

After a guard period of Tr^ir seconds a RESET ACKNOWLEDGE message shall be returned to the UTRAN indicating 
that all references have been cleared. 

When a RESET ACKNOWLEDGE message is sent from a CN node towards an RNC for which the sending CN node is 
not the default CN node, the Global CN-ID IE shall be included. 

Interactions with other procedures: 

In case of interactions with other procedures, the Reset procedure shall always override all other procedures. 

8.26.3 Abnormal Conditions 

8.26.3.1 Abnormal Condition at the CN 

If the CN sends a RESET message to the RNC and receives no RESET ACKNOWLEDGE message within a period 
TRafR then it shall repeat the entire Reset procedure. The sending of the RESET message shall be repeated a maximum 
of "n" times where n is an operator matter. After the n-th unsuccessful repetition the procedure shall be stopped and e.g. 
the maintenance system be informed. 

8.26.3.2 Abnormal Condition at the UTRAN 

If the RNC sends a RESET message to the CN and receives no RESET ACKNOWLEDGE message within a period 
TRafc then it shall repeat the entire Reset procedure. The sending of the RESET message shall be repeated a maximum 
of "n" times where n is an operator matter. After the n-th unsuccessful repetition the procedure shall be stopped and e.g. 
the maintenance system be informed. 

8.26.3.3 Crossing of Reset IVIessages 

When an entity that has sent a RESET message and is waiting for a RESET ACKNOWLEDGE message, instead 
receives a RESET message from the peer entity, it shall stop timer T^afc or TRat^ and send a RESET ACKNOWLEDGE 
message to the peer entity. 

8.27 Error Indication 
8.27.1 General 

The Error Indication procedure is initiated by a node to report detected errors in one incoming message, provided they 
cannot be reported by an appropriate failure message. 

If the error situation arises due to reception of a message utilising dedicated signalling, then the Error Indication 
procedure uses connection oriented signalling. Otherwise the procedure uses connectionless signalling. 



8.27.2 Successful Operation 



RNC 



ON 



ERROR INDICATION 

< 




Figure 31: Error Indication procedure, CN originated. Successful operation. 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



55 



ETSI TS 125 413 V4.10.0 (2003-09) 



RNC 



CN 



ERROR INDICATION 



1 



Figure 32: Error Indication procedure, RNC originated. Successful operation. 

When the conditions defined in clause 10 are fulfilled, the Error Indication procedure is initiated by an ERROR 
INDICATION message sent from the receiving node. 

The ERROR INDICATION message shall contain at least either the Cause IE or the Criticality Diagnostics IE. 

If the ERROR INDICATION message is sent connectionless, the CN Domain Indicator l¥. shall be present. 

If the ERROR INDICATION message is sent connectionless towards the CN, the Global RNC-ID IE shall be present. 

Examples for possible cause values for protocol error indications are: 

"Transfer Syntax Error". 

"Semantic Error". 

"Message not compatible with receiver state". 

When an ERROR INDICATION message is sent connectionless from a CN node towards an RNC for which the 
sending CN node is not the default CN node, the Global CN-ID IE shall be included. 

8.27.3 Abnormal Conditions 

Not applicable. 

8.28 CN Deactivate Trace 
8.28.1 General 

The purpose of the CN Deactivate Trace procedure is to inform the RNC that it should stop producing a trace record for 
the indicated trace reference. The procedure uses the connection oriented signalling. 



8.28.2 Successful Operation 

RNC 



CN 



CN DEACTIVATE 
TRACE 



Figure 33: CN Deactivate Trace procedure. Successful operation. 

The CN Deactivate Trace procedure is invoked by the CN sending a CN DEACTIVATE TRACE message to the 
UTRAN. 

The CN DEACTIVATE TRACE message shall contain the Trace Reference IE and may contain the Trigger ID IE. The 
Trace Reference IE and, if present, the Trigger ID IE are used to indicate which trace shall be stopped. 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



56 



ETSI TS 125 413 V4.10.0 (2003-09) 



8.28.3 Abnormal Conditions 

If the RNC receives a CN DEACTIVATE TRACE message with an unknown trace reference, the RNC shall take no 
action. 

8.29 Reset Resource 

8.29.1 General 

The purpose of the Reset Resource procedure is to initialise part of the UTRAN in the event of an abnormal failure in 
the CN or vice versa (e.g. Signalling Transport processor reset). The procedure uses connectionless signalling. 

8.29.1 .1 Reset Resource procedure initiated from the RNC 

Void 

8.29.1 .2 Reset Resource procedure initiated from the CN 

Void. 

8.29.2 Successful Operation 

8.29.2.1 Reset Resource procedure initiated from the RNC 



RNC 



CN 



RESET RESOURCE 



RESET RESOURCE 
ACKNOWLEDGE 



Figure 34: RNC initiated Reset Resource procedure. Successful operation. 

The RNC initiates this procedure by sending a RESET RESOURCE message to the CN. 

The RESET RESOURCE message shall include the CN Domain Indicator IE, the Global RNC-ID IE, the Cause IE 
with appropriate cause value (e.g. "Signalling Transport Resource Failure") and a list containing lu Signalling 
Connection Identifier lEs. 

On reception of this message the CN shall release locally the resources and references (i.e. resources and lu signalling 
connection identifiers) associated to the lu signalling connection identifiers indicated in the received message. The CN 
shall always return the RESET RESOURCE ACKNOWLEDGE message to the RNC when all lu-related resources and 
references have been released and shall include the CN Domain Indicator IE and a list of lu Signalling Connection 
Identifier lEs. The list of /m Signalling Connection Identifier lEs within the RESET RESOURCE ACKNOWLEDGE 
message shall be in the same order as received in the RESET RESOURCE message. Unknown signalling connection 
identifiers shall be reported as released. 

When a RESET RESOURCE ACKNOWLEDGE message is sent from a CN node towards an RNC for which the 
sending CN node is not the default CN node, the Global CN-ID IE shall be included. 

Both CN and RNC shall provide means to prevent the immediate re-assignment of released lu signalling connection 
identifiers to minimise the risk that the Reset Resource procedure releases the same lu signalling connection identifiers 
re-assigned to new lu connections. 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



57 



ETSI TS 125 413 V4.10.0 (2003-09) 



8.29.2.2 Reset Resource procedure initiated from the CN 



RNC 



CN 



RESET RESOURCE 



RESET RESOURCE 
ACKNOWLEDGE 



Figure 35: CN initiated Reset Resource procedure. Successful operation. 

The CN initiates this procedure by sending a RESET RESOURCE message to the RNC. 

The RESET RESOURCE message shall include the CN Domain Indicator IE, the Cause IE with appropriate cause 
value (e.g. "Signalling Transport Resource Failure") and a list containing lu Signalling Connection Identifier lEs. 

When a RESET RESOURCE message is sent from a CN node towards an RNC for which the sending CN node is not 
the default CN node, the Global CN-ID IE shall be included. 

On reception of this message the RNC shall release locally the resources and references (i.e. radio resources and lu 
signalling connection identifiers) associated to the specific CN node and lu signalling connection identifiers indicated in 
the received message. The Global RNC-ID IE shall not be included in the RESET RESOURCE message. If no Global 
CN-ID IE is included in the RESET RESOURCE message to indicate the sending CN node, the default CN node for the 
indicated CN domain shall be considered as sender. The RNC shall always return the RESET RESOURCE 
ACKNOWLEDGE message to the CN when all lu-related resources and references have been released and shall 
include the CN Domain Indicator IE, a list of /« Signalling Connection Identifier lEs and the Global RNC-ID IE. The 
list of /m Signalling Connection Identifier lEs within the RESET RESOURCE ACKNOWLEDGE message shall be in 
the same order as received in the RESET RESOURCE message. Unknown signalling connection identifiers shall be 
reported as released. 

Both RNC and CN shall provide means to prevent the immediate re-assignment of released lu signalling connection 
identifiers to minimise the risk that the Reset Resource procedure releases the same lu signalling connection identifiers 
re-assigned to new lu connections. 

8.30 RAB Modification Request 

8.30.1 General 

The purpose of the RAB Modification procedure is to allow RNC to initiate renegotiation of RABs for a given UE after 
RAB establishment. The procedure uses connection oriented signalling. 

8.30.2 Successful Operation 



RNC 



CN 



RAB MODIFY 
REQUEST 



Figure 36: RAB Modification procedure. 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



58 



ETSI TS 125 413 V4.10.0 (2003-09) 



The RNC shall initiate the procedure by generating a RAB MODIFY REQUEST message towards the CN and shall 
include a list of RAB s To Be Modified lEs. For each RAB requested to be modified the RABs To Be Modified Item IE of 
the RAB MODIFY REQUEST message shall include the RAB ID IE, and the corresponding Requested RAB Parameter 
Values IE. The Requested RAB Parameter Values IE shall list those RAB parameters the RNC would like modified and 
the associated new RAB parameter values it is requesting. For any given RAB, RNC shall be able to propose 
modifications to any negotiable RAB parameters. 

Upon reception of the RAB MODIFY REQUEST message, it is up to the CN to decide how to react to the request. 

8.30.3 Abnormal Conditions 

Not applicable. 

8.31 Location Related Data 
8.31.1 General 

The purpose of the Location Related Data procedure is to provide the means to handle additional Location related 
requests over the lu interface: it allows the CN to either retrieve from the RNC deciphering keys (to be forwarded to the 
UE) for the broadcasted assistance data, or request the RNC to deliver dedicated assistance data to the UE. The 
procedure uses connection oriented signalling. 



8.31.2 Successful Operation 



RNC 



CN 



LOCATION RELATED DATA 
REOUEST 



LOCATION RELATED DATA 
RESPONSE 



Figure 37: Location Related Data procedure. Successful operation. 

The CN initiates the procedure by generating an LOCATION RELATED DATA REQUEST message to the RNC. 

Upon the reception of the LOCATION RELATED DATA REQUEST message, the RNC shall initiate requested 
function as indicated in the Location Related Data Request Type IE. 

The Location Related Data Request Type IE shall indicate to the RNC whether: 

to start dedicated assistance data delivery to the UE, or 

to send deciphering keys for broadcast assistance data to the CN. 

If the LOCATION RELATED DATA REQUEST message included a request for dedicated assistance data delivery to 
the UE, and if the dedicated assistance data was successfully delivered to the UE, the RNC shall respond to CN with 
LOCATION RELATED DATA RESPONSE message containing no data. 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



59 



ETSI TS 125 413 V4.10.0 (2003-09) 



If the LOCATION RELATED DATA REQUEST message included a request for broadcast assistance data deciphering 
keys, the RNC shall respond to CN with LOCATION RELATED DATA RESPONSE message containing the 
Broadcast Assistance Data Deciphering Keys IE. 

8.31.3 Unsuccessful Operation 



RNC 



CN 



LOCATION RELATED DATA 
REOUEST 



LOCATION RELATED DATA 
FAILURE 



Figure 38: Location Related Data procedure. Unsuccessful operation. 

If the RNC was not able to successfully deliver the requested dedicated assistance data to the UE, or if the RNC is not 
able to provide the requested deciphering keys, the RNC shall send LOCATION RELATED DATA FAILURE message 
including Cause IE to the CN. The Cause IE shall indicate the appropriate cause value to CN, e.g. "Dedicated 
Assistance data Not Available" or "Deciphering Keys Not Available". 

8.31.4 Abnormal Conditions 

Not applicable. 



9 Elements for RANAP Communication 

9.1 IVIessage Functional Definition and Content 
9.1.1 General 

Subclause 9.1 presents the contents of RANAP messages in tabular format. The corresponding ASN.l definition is 
presented in subclause 9.3. In case there is contradiction between the tabular format in subclause 9.1 and the ASN.l 
definition, the ASN.l shall take precedence, except for the definition of conditions for the presence of conditional lEs, 
where the tabular format shall take precedence. 

NOTE: The messages have been defined in accordance to the guidelines specified in [18]. 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



60 



ETSI TS 125 413 V4.10.0 (2003-09) 



9.1 .2 Message Contents 



9.1.2.1 



Presence 



All information elements in the message descriptions below are marked mandatory, optional or conditional according to 
table 4. 

Table 4: Meaning of abbreviations used in RANAP messages 



Abbreviation 


Meaning 


IVI 


lEs marked as Mandatory (M) shall always be included in the 
message. 





lEs marked as Optional (0) may or may not be included in the 
message. 


c 


lEs marked as Conditional (C) shall be included in a message only if 
the condition is satisfied. Otherwise the IE shall not be included. 



9.1.2.2 



Criticality 



Each Information Element or Group of Information Elements may have criticality information applied to it. 
Following cases are possible: 

Table 5: Meaning of content within "Criticality" column 



Abbreviation 


Meaning 


- 


No criticality information is applied explicitly. 


YES 


Criticality information is applied. This is usable only for non- 
repeatable lEs 


GLOBAL 


The IE and all its repetitions together have one common criticality 
information. This is usable only for repeatable lEs. 


EACH 


Each repetition of the IE has its own criticality information. It is not 
allowed to assign different criticality values to the repetitions. This is 
usable only for repeatable lEs. 



9.1.2.3 Range 

The Range column indicates the allowed number of copies of repetitive lEs/IE groups. 

9.1.2.4 Assigned Criticality 

This column provides the actual criticality information as defined in subclause 10.3.2, if applicable. 

9.1 .3 RAB ASSIGNMENT REQUEST 

This message is sent by the CN to request the establishment, modification or release of one or more RABs for the same 
UE. 

Direction: CN -^ RNC. 

Signalling bearer mode: Connection oriented. 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



61 



ETSI TS 125 413 V4.10.0 (2003-09) 



IE/Group Name 


Presence 


Range 


IE type and 
reference 


Semantics 
description 


Criticality 


Assigned 
Criticality 


IVIessage Type 


M 




9.2.1.1 




YES 


reject 


RABs To Be Setup Or 
Modified List 











YES 


ignore 


>RABs To Be Setup 
Or Modified Item IBs 




1 to 
<maxnoofRABs> 










»First Setup Or 
Modify Item 


M 






Grouping 
reason: 
same 
criticality 


EACH 


reject 


»>RAB ID 


M 




9.2.1.2 


The same 
RAB ID must 
only be 
present in 
one group. 






»>NAS 

Synchronisation 

Indicator 







9.2.3.18 








»>RAB 
Parameters 







9.2.1.3 


Includes all 
necessary 
parameters 
for RABs 
(both for 
MSC and 
SGSN) 
including 
QoS. 






»>User Plane 
Information 











- 




»»User Plane 
IVIode 


M 




9.2.1.18 








»»UP Mode 
Versions 


M 




9.2.1.19 




" 




»>Transport 
Layer Information 











- 




»»Transport 
Layer Address 


M 




9.2.2.1 




- 




»»lu 
Transport 
Association 


M 




9.2.2.2 








»>Service 
Handover 







9.2.1.41 




- 




»Second Setup Or 
Modify Item 


M 






Grouping 
reason: 
same 
criticality 


EACH 


ignore 


>» PDP Type 
Information 







9.2.1.40 




- 




»>Data Volume 

Reporting 

Indication 







9.2.1.17 








»>DL GTP-PDU 
Sequence Number 







9.2.2.3 




- 




»>UL GTP-PDU 
Sequence Number 







9.2.2.4 




- 




»>DL N-PDU 
Sequence Number 







9.2.1.33 




- 




»>UL N-PDU 
Sequence Number 







9.2.1.34 




- 




»>Alternative 
RAB Parameter 
Values 







9.2.1.43 




YES 


ignore 


RABs To Be Released 
List 











YES 


ignore 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



62 



ETSI TS 125 413 V4.10.0 (2003-09) 



IE/Group Name 


Presence 


Range 


IE type and 
reference 


Semantics 
description 


Criticality 


Assigned 
Criticality 


>RABs To Be 
Released Item IBs 




1 to 
<maxnoofRABs> 






EACH 


ignore 


»RAB ID 


M 




9.2.1.2 


The same 
RAB ID must 
only be 
present in 
one group. 






»Cause 


M 




9.2.1.4 




- 





Range bound 


Explanation 


maxnoofRABs 


Maximum no. of RABs for one UE. Value is 256. 



9.1 .4 RAB ASSIGNMENT RESPONSE 

This message is sent by the RNC to report the outcome of the request from the RAB ASSIGNMENT REQUEST 

message. 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



63 



ETSI TS 125 413 V4.10.0 (2003-09) 



Direction: RNC -^ CN. 

Signalling bearer mode: Connection oriented. 



IE/Group Name 


Presence 


Range 


IB type and 
reference 


Semantics 
description 


Criticality 


Assigned 
Criticality 


Message Type 


M 




9.2.1.1 




YES 


reject 


RABs Setup Or lUlodified 
List 











YES 


ignore 


>RABs Setup Or 
lUlodified Item IBs 




1 to 
<maxnoofRABs> 






EACH 


ignore 


»RAB ID 


M 




9.2.1.2 


The same 
RAB ID must 
only be 
present in 
one group. 






»Transport Layer 
Address 







9.2.2.1 




- 




»lu Transport 
Association 







9.2.2.2 




- 




»DL Data Volumes 











- 




»>Data Volume 
List 




1 to 

<maxnoofVol> 






- 




»»Unsuccessful 
ly Transmitted DL 
Data Volume 


M 




9.2.3.12 








»»Data Volume 
Reference 







9.2.3.13 




- 




»Assigned RAB 
Parameter Values 







9.2.1.44 




YES 


ignore 


RABs Released List 











YES 


ignore 


>RABs Released Item 
lEs 




1 to 
<maxnoofRABs> 






EACH 


ignore 


»RAB ID 


M 




9.2.1.2 


The same 
RAB ID must 
only be 
present in 
one group. 






»DL Data Volumes 











- 




»>Data Volume 
List 




1 to 
<maxnoofVol> 






- 




»»Unsuccessful 
ly Transmitted DL 
Data Volume 


M 




9.2.3.12 








»»Data Volume 
Reference 







9.2.3.13 




- 




»DLGTP-PDU 
Sequence Number 







9.2.2.3 




- 




»ULGTP-PDU 
Sequence Number 







9.2.2.4 




- 




RABs Queued List 











YES 


ignore 


>RABs Queued Item 
lEs 




1 to 
<maxnoofRABs> 






EACH 


ignore 


»RAB ID 


M 




9.2.1.2 


The same 
RAB ID must 
only be 
present in 
one group. 






RABs Failed To Setup Or 
Modify List 











YES 


ignore 


>RABs Failed To 
Setup Or Modify Item 
IBs 




1 to 
<maxnoofRABs> 






EACH 


ignore 


»RAB ID 


M 




9.2.1.2 


The same 
RAB ID must 
only be 
present in 







£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



64 



ETSI TS 125 413 V4.10.0 (2003-09) 











one group. 






»Cause 


M 




9.2.1.4 




- 




RABs Failed To Release 
List 











YES 


ignore 


>RABs Failed To 
Release Item lEs 




1 to 
<maxnoofRABs> 






EACH 


ignore 


»RAB ID 


M 




9.2.1.2 


The same 
RAB ID must 
only be 
present in 
one group. 






»Cause 


M 




9.2.1.4. 




- 




Criticality Diagnostics 







9.2.1.35 




YES 


ignore 



Range bound 


Explanation 


maxnoofRABs 


Maximum no. of RABs for one UE. Value is 256. 


maxnoofVol 


Maximum no. of reported data volume for one RAB. Value is 2. 



9.1 .5 RAB RELEASE REQUEST 

This message is sent by the RNC, to request the CN to release one or more RABs for the same UE. 

Direction: RNC -^ CN. 

Signalling bearer mode: Connection oriented. 



IE/Group Name 


Presence 


Range 


IE type and 
reference 


Semantics 
description 


Criticality 


Assigned 
Criticality 


Message Type 


M 




9.2.1.1 




YES 


ignore 


RABs To Be Released 
List 


M 








YES 


ignore 


>RABs To Be 
Released Item lEs 




1 to 
<maxnoofRABs> 






EACH 


ignore 


»RAB ID 


M 




9.2.1.2 




- 




»Cause 


M 




9.2.1.4 




- 





Range bound 


Explanation 


maxnoofRABs 


Maximum no. of RABs for one UE. Value is 256. 



9.1 .6 lU RELEASE REQUEST 

This message is sent by the RNC to request the CN to release the lu connection. 

Direction: RNC -^ CN. 

Signalling bearer mode: Connection oriented. 



IE/Group Name 


Presence 


Range 


IE type and 
reference 


Semantics 
description 


Criticality 


Assigned 
Criticality 


Message Type 


M 




9.2.1.1 




YES 


ignore 


Cause 


M 




9.2.1.4 




YES 


ignore 



9.1 .7 lU RELEASE COMMAND 

This message is sent by the CN to order RNC to release all resources related to the lu connection. 

Direction: CN -^ RNC. 

Signalling bearer mode: Connection oriented. 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



65 



ETSI TS 125 413 V4.10.0 (2003-09) 



IE/Group Name 


Presence 


Range 


IE type and 
reference 


Semantics 
description 


Criticality 


Assigned 
Criticality 


Message Type 


M 




9.2.1.1 




YES 


reject 


Cause 


M 




9.2.1.4 




YES 


ignore 



9.1 .8 lU RELEASE COMPLETE 

This message is sent by the RNC as response to the lU RELEASE COMMAND message. 

Direction: RNC -^ CN. 

SignalHng bearer mode: Connection oriented. 



IE/Group Name 


Presence 


Range 


IE type and 
reference 


Semantics 
description 


Criticality 


Assigned 
Criticality 


Message Type 


M 




9.2.1.1 




YES 


reject 


RABs Data Volume 
Report List 











YES 


ignore 


>RABs Data Volume 
Report Item lEs 




1 to 
<maxnoofRABs> 






EACH 


ignore 


»RAB ID 


M 




9.2.1.2 




~ 




»RAB Data 
Volume Report List 


M 








- 




»>RAB Data 
Volume Report 
Item lEs 




1 to 
<maxnoofVol> 










»»Unsuccessfull 
y Transmitted DL 
Data 
Volume 


M 




9.2.3.12 








»»Data Volume 
Reference 







9.2.3.13 




- 




RABs Released List 











YES 


ignore 


>RABs Released Item 
lEs 




1 to 
<maxnoofRABs> 






EACH 


ignore 


»RAB ID 


M 




9.2.1.2 




- 




»DLGTP-PDU 
Sequence Number 







9.2.2.3 




- 




»ULGTP-PDU 
Sequence Number 







9.2.2.4 




- 




Criticality Diagnostics 







9.2.1.35 




YES 


ignore 




















Range bound 


Explanation 






maxnoofRABs 


Maximum no. o 


RABs for one UE. Value is 256 










maxnoofVol 


Maximum no. o 


reported data volume for one R 


AB. Value is 2. 







9.1 .9 RELOCATION REQUIRED 

This message is sent by the source RNC to inform the CN that a relocation is to be performed. 

Direction: RNC -^ CN. 

SignalHng bearer mode: Connection oriented. 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



66 



ETSI TS 125 413 V4.10.0 (2003-09) 



IE/Group Name 


Presence 


Range 


IE type and 
reference 


Semantics 
description 


Criticality 


Assigned 
Criticality 


Message Type 


M 




9.2.1.1 




YES 


reject 


Relocation Type 


M 




9.2.1.23 




YES 


reject 


Cause 


M 




9.2.1.4 




YES 


ignore 


Source ID 


M 




9.2.1.24 




YES 


ignore 


Target ID 


M 




9.2.1.25 




YES 


reject 


MS Classmark 2 


C- 

ifGSMtarget 




9.2.1.26 


As defined in 
[10]. 


YES 


reject 


MS Classmark 3 


C- 

ifOSMtarget 




9.2.1.27 


As defined in 
[10]. 


YES 


ignore 


Source RNC To Target 
RNC Transparent 
Container 


C- 

ifUMTStarge 

t 




9.2.1.28 




YES 


reject 


Old BSS To New BSS 
Information 







9.2.1.29 


Coded as 
the Old BSS 
to New BSS 
information 
elements 
field of the 
Old BSS to 
New BSS 
Information 
IE defined in 
[11]. Can 
optionally be 
used if GSM 
target but 
not used for 
UMTS 
target. 


YES 


ignore 



Condition 


Explanation 


ifGSMtarget 


This IE shall be present if the Target ID IE contains a CGI IE. 


ifUMTStarget 


This IE shall be presentif the Target ID IE contains a Target RNC-ID 
IE. 



9.1.10 RELOCATION REQUEST 

This message is sent by the CN to request the target RNC to allocate necessary resources for a relocation. 

Direction: CN -^ RNC. 

Signalling bearer mode: Connection oriented. 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



67 



ETSI TS 125 413 V4.10.0 (2003-09) 



IE/Group Name 


Presence 


Range 


IE type and 
reference 


Semantics 
description 


Criticality 


Assigned 
Criticality 


Message Type 


M 




9.2.1.1 




YES 


reject 


Permanent NAS UE 
Identity 







9.2.3.1 




YES 


ignore 


Cause 


M 




9.2.1.4 




YES 


ignore 


CN Domain Indicator 


M 




9.2.1.5 




YES 


reject 


Source RNC To Target 
RNC Transparent 
Container 


M 




9.2.1.28 




YES 


reject 


RABs To Be Setup List 











YES 


reject 


>RABs To Be Setup 
Item lEs 




1 to 
<maxnoofRABs> 






EACH 


reject 


»RAB ID 


M 




9.2.1.2 




- 




»NAS 

Synchronisation 

Indicator 







9.2.3.18 








»RAB Parameters 


M 




9.2.1.3 




- 




»Data Volume 

Reporting 

Indication 


C - ifPS 




9.2.1.17 








» PDP Type 
Information 


C - ifPS 




9.2.1.40 




- 




»User Plane 
Information 


M 








- 




»>User Plane 
Mode 


M 




9.2.1.18 




- 




»>UP Mode 
Versions 


M 




9.2.1.19 








»Transport Layer 
Address 


M 




9.2.2.1 








»lu Transport 
Association 


M 




9.2.2.2 




- 




»Service Handover 







9.2.1.41 




- 




» Alternative RAB 
Parameter Values 







9.2.1.43 




YES 


Ignore 


Integrity Protection 
Information 







9.2.1.11 


Integrity 

Protection 

Information 

includes key 

and 

permitted 

algorithms. 


YES 


ignore 


Encryption Information 







9.2.1.12 


Encryption 

Information 

includes key 

and 

permitted 

algorithms. 


YES 


ignore 


lu Signalling Connection 
Identifier 


M 




9.2.1.38 




YES 


ignore 


Global CN-ID 







9.2.1.46 




YES 


reject 



Condition 


Explanation 






IfPS 


This IE shall be present if the CN domain indicator IE is set to "PS 
domain". 



Range bound 


Explanation 


maxnoofRABs 


Maximum no. of RABs for one UE. Value is 256. 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



68 



ETSI TS 125 413 V4.10.0 (2003-09) 



9.1 .11 RELOCATION REQUEST ACKNOWLEDGE 

This message is sent by the target RNC to inform the CN about the result of the resource allocation for the requested 
relocation. 

Direction: RNC -^ CN. 

Signalling bearer mode: Connection oriented. 



IE/Group Name 


Presence 


Range 


IE type and 
reference 


Semantics 
description 


Criticality 


Assigned 
Criticality 


Message Type 


M 




9.2.1.1 




YES 


reject 


Target RNC To Source 
RNC Transparent 
Container 







9.2.1.30 




YES 


ignore 


RABs Setup List 











YES 


ignore 


>RABs Setup Item 
lEs 




1 to 
<maxnoofRABs> 






EACH 


reject 


»RAB ID 


M 




9.2.1.2 




- 




»Transport Layer 
Address 







9.2.2.1 




- 




»lu Transport 
Association 







9.2.2.2 




- 




»Assigned RAB 
Parameter Values 







9.2.1.44 




YES 


ignore 


RABs Failed To Setup 
List 











YES 


ignore 


>RABs Failed To 
Setup Item lEs 




1 to 
<maxnoofRABs> 






EACH 


ignore 


»RAB ID 


M 




9.2.1.2 




- 




»Cause 


M 




9.2.1.4 




- 




Chosen Integrity Protection 
Algorithm 







9.2.1.13 


Indicates the 
Integrity 
Protection 
algorithm 
that will be 
used by the 
target RNC. 


YES 


ignore 


Chosen Encryption 
Algorithm 







9.2.1.14 


Indicates the 
Encryption 
algorithm 
that will be 
used by the 
target RNC. 


YES 


ignore 


Criticality Diagnostics 







9.2.1.35 




YES 


ignore 



Range bound 


Explanation 


maxnoofRABs 


IVIaximum no. of RABs for one UE. Value is 256. 



9.1.12 RELOCATION COMMAND 

This message is sent by the CN to source RNC to inform that resources for the relocation are allocated in target RNC. 

Direction: CN -^ RNC. 

Signalling bearer mode: Connection oriented. 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



69 



ETSI TS 125 413 V4.10.0 (2003-09) 



IE/Group Name 


Presence 


Range 


IE type and 
reference 


Semantics 
description 


Criticality 


Assigned 
Criticality 


Message Type 


M 




9.2.1.1 




YES 


reject 


Target RNC To Source RNC 
Transparent Container 







9.2.1.30 




YES 


reject 


L3 Information 







9.2.1.31 


Coded as 
the value 
part of the 
Layer 3 
Information 
IE defined in 
[11] (i.e. 
excluding 
the Element 
Identifier and 
the Lengtfi 
fields). 


YES 


ignore 


RABs To Be Released List 











YES 


ignore 


>RABs To Be Released 
Item lEs 




1 to 
<maxnoofRABs> 






EACH 


ignore 


»RAB ID 


M 




9.2.1.2 




- 




RABs Subject To Data 
Forwarding List 











YES 


ignore 


>RABs Subject To Data 
Forwarding Item lEs 




1 to 
<maxnoofRABs> 






EACH 


ignore 


»RAB ID 


M 




9.2.1.2 




- 




»Transport Layer 
Address 


M 




9.2.2.1 




- 




»lu Transport 
Association 


M 




9.2.2.2 




- 




Criticality Diagnostics 







9.2.1.35 




YES 


ignore 



Range bound 


Explanation 


maxnoofRABs 


Maximum no. of RABs for one UE. Value is 256. 



9.1.13 RELOCATION DETECT 

This message is sent by the target RNC to inform the CN that the relocation execution trigger has been received. 

Direction: RNC -^ CN. 

SignalHng bearer mode: Connection oriented. 



IE/Group Name 


Presence 


Range 


IE type and 
reference 


Semantics 
description 


Criticality 


Assigned 
Criticality 


Message Type 


M 




9.2.1.1 




YES 


Ignore 



9.1.14 RELOCATION COMPLETE 

This message is sent by the target RNC to inform the CN that the relocation is completed. 

Direction: RNC -^ CN. 

Signalling bearer mode: Connection oriented. 



IE/Group Name 


Presence 


Range 


IE type and 
reference 


Semantics 
description 


Criticality 


Assigned 
Criticality 


Message Type 


M 




9.2.1.1 




YES 


ignore 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



70 



ETSI TS 125 413 V4.10.0 (2003-09) 



9.1.15 RELOCATION PREPARATION FAILURE 



This message is sent by the CN to the source RNC if the relocation preparation failed. 

Direction: CN -^ RNC. 

Signalling bearer mode: Connection oriented. 



IE/Group Name 


Presence 


Range 


IE type and 
reference 


Semantics 
description 


Criticality 


Assigned 
Criticality 


Message Type 


M 




9.2.1.1 




YES 


reject 


Cause 


M 




9.2.1.4 




YES 


ignore 


Criticality Diagnostics 







9.2.1.35 




YES 


ignore 



9.1.16 RELOCATION FAILURE 

This message is sent by the target RNC to inform the CN that the requested resource allocation failed. 

Direction: RNC -^ CN. 

Signalling bearer mode: Connection oriented. 



IE/Group Name 


Presence 


Range 


IE type and 
reference 


Semantics 
description 


Criticality 


Assigned 
Criticality 


IVIessage Type 


M 




9.2.1.1 




YES 


reject 


Cause 


M 




9.2.1.4 




YES 


ignore 


Criticality Diagnostics 







9.2.1.35 




YES 


ignore 



9.1.17 RELOCATION CANCEL 

This message is sent by the source RNC to the CN to cancel an ongoing relocation. 

Direction: RNC -^ CN. 

Signalling bearer mode: Connection oriented. 



IE/Group Name 


Presence 


Range 


IE type and 
reference 


Semantics 
description 


Criticality 


Assigned 
Criticality 


IVIessage Type 


M 




9.2.1.1 




YES 


reject 


Cause 


M 




9.2.1.4 




YES 


ignore 



9.1.18 RELOCATION CANCEL ACKNOWLEDGE 

This message is sent by the CN to the source RNC when the relocation has been cancelled. 

Direction: CN -^ RNC. 

Signalling bearer mode: Connection oriented. 



IE/Group Name 


Presence 


Range 


IE type and 
reference 


Semantics 
description 


Criticality 


Assigned 
Criticality 


IVIessage Type 


M 




9.2.1.1 




YES 


reject 


Criticality Diagnostics 







9.2.1.35 




YES 


ignore 



9.1.19 SRNS CONTEXT REQUEST 

This message is sent by the CN to source RNC to indicate the PS RABs for which context transfer shall be performed. 
Direction: CN -^ RNC. 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



71 



ETSI TS 125 413 V4.10.0 (2003-09) 



Signalling bearer mode: Connection oriented. 



IE/Group Name 


Presence 


Range 


IE type and 
reference 


Semantics 
description 


Criticality 


Assigned 
Criticality 


Message Type 


M 




9.2.1.1 




YES 


reject 


RABs Subject To Data 
Forwarding List 


M 








YES 


ignore 


>RABs Subject To 
Data Forwarding Item 
IBs 




1 to 
<maxnoofRABs> 






EACH 


reject 


»RAB ID 


M 




9.2.1.2 




- 





Range bound 


Explanation 


maxnoofRABs 


Maximum no. of RABs for one UE. Value is 256. 



9.1 .20 SRNS CONTEXT RESPONSE 

This message is sent by the source RNC as a response to SRNS CONTEXT REQUEST message. 

Direction: RNC -^ CN. 

Signalling bearer mode: Connection oriented. 



IE/Group Name 


Presence 


Range 


IE type and 
reference 


Semantics 
description 


Criticality 


Assigned 
Criticality 


Message Type 


M 




9.2.1.1 




YES 


reject 


RABs Contexts List 











YES 


ignore 


>RABs Contexts Item 
lEs 




1 to 
<maxnoofRABs> 






EACH 


ignore 


»RAB ID 


M 




9.2.1.2 




- 




»DLGTP-PDU 
Sequence Number 







9.2.2.3 




- 




»ULGTP-PDU 
Sequence Number 







9.2.2.4 




- 




»DLN-PDU 
Sequence Number 







9.2.1.33 




- 




»ULN-PDU 
Sequence Number 







9.2.1.34 




- 




RABs Contexts Failed To 
Transfer List 











YES 


ignore 


>RABs Contexts 
Failed To Transfer 
Item lEs 




1 to 
<maxnoofRABs> 






EACH 


ignore 


»RAB ID 


M 




9.2.1.2 




- 




»Cause 


M 




9.2.1.4 




- 




Criticality Diagnostics 







9.2.1.35 




YES 


ignore 




















Range bound 


Explanation 






maxnoofRABs 


Maximum no. of 


RABs for one UE. Value is 256 









9.1 .21 SRNS DATA FORWARD COMMAND 

This message is sent by the CN to the RNC to trigger the transfer of N-PDUs from the RNC to the CN in intersystem 
change or in some further cases described in [21]. 

Direction: CN -^ RNC. 

Signalling bearer mode: Connection oriented. 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



72 



ETSI TS 125 413 V4.10.0 (2003-09) 



IE/Group Name 


Presence 


Range 


IE type and 
reference 


Semantics 
description 


Criticality 


Assigned 
Criticality 


Message Type 


M 




9.2.1.1 




YES 


ignore 


RABs Subject To Data 
Forwarding List 











YES 


ignore 


>RABs Subject To 
Data Forwarding Item 
IBs 




1 to 
<maxnoofRABs> 






EACH 


ignore 


»RAB ID 


M 




9.2.1.2 




- 




»Transport Layer 
Address 


M 




9.2.2.1 




- 




»lu Transport 
Association 


M 




9.2.2.2 




- 





Range bound 


Explanation 


maxnoofRABs 


IVlaximum no. of RABs for one UE. Value is 256. 



9.1 .22 FORWARD SRNS CONTEXT 

This message is sent either by source RNC to the CN or by the CN to target RNC. 
Direction: CN -^ RNC and RNC -^ CN. 
Signalling bearer mode: Connection oriented. 



IE/Group Name 


Presence 


Range 


IE type and 
reference 


Semantics 
description 


Criticality 


Assigned 
Criticality 


IVlessage Type 


M 




9.2.1.1 




YES 


ignore 


RAB Contexts List 


M 








YES 


ignore 


>RAB Contexts Item 
lEs 




1 to 
<maxnoofRABs> 






EACH 


ignore 


»RAB ID 


M 




9.2.1.2 




- 




»DL GTP-PDU 

Sequence 

Number 







9.2.2.3 








»UL GTP-PDU 

Sequence 

Number 







9.2.2.4 








»DLN-PDU 
Sequence Number 







9.2.1.33 




- 




»ULN-PDU 
Sequence Number 







9.2.1.34 




- 





Range bound 


Explanation 


maxnoofRABs 


IVlaximum no. of RABs for one UE. Value is 256. 



9.1.23 PAGING 

This message is sent by the CN to request UTRAN to page a specific UE. 

Direction: CN -^ RNC. 

Signalling bearer mode: Connectionless. 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



73 



ETSI TS 125 413 V4.10.0 (2003-09) 



IE/Group Name 


Presence 


Range 


IE type and 
reference 


Semantics 
description 


Criticality 


Assigned 
Criticality 


Message Type 


M 




9.2.1.1 




YES 


ignore 


CN Domain Indicator 


M 




9.2.1.5 




YES 


ignore 


Permanent NAS UE Identity 


M 




9.2.3.1 




YES 


ignore 


Temporary UE Identity 







9.2.3.2 




YES 


ignore 


Paging Area ID 







9.2.1.21 




YES 


ignore 


Paging Cause 







9.2.3.3 




YES 


ignore 


Non Searching Indication 







9.2.1.22 




YES 


ignore 


DRX Cycle Length 
Coefficient 







9.2.1.37 




YES 


ignore 



9.1.24 COMMON ID 

This message is sent by the CN to inform RNC about the permanent NAS UE identity for a user. 

Direction: CN -^ RNC. 

SignalHng bearer mode: Connection oriented. 



IE/Group Name 


Presence 


Range 


IE type and 
reference 


Semantics 
description 


Criticality 


Assigned 
Criticality 


IVIessage Type 


M 




9.2.1.1 




YES 


ignore 


Permanent NAS UE Identity 


M 




9.2.3.1 




YES 


ignore 



9.1.25 CN INVOKE TRACE 

This message is sent by the CN to request the RNC to start to produce a trace record. 

Direction: CN -^ RNC. 

Signalling bearer mode: Connection oriented. 



IE/Group Name 


Presence 


Range 


IE type and 
reference 


Semantics 
description 


Criticality 


Assigned 
Criticality 


IVIessage Type 


M 




9.2.1.1 




YES 


ignore 


Trace Type 


M 




9.2.1.6 




YES 


ignore 


Trace Reference 


M 




9.2.1.8 




YES 


ignore 


Trigger ID 







9.2.1.7 




YES 


ignore 


UE Identity 







9.2.1.9 




YES 


ignore 


OMCID 







9.2.1.10 




YES 


ignore 



9.1 .26 SECURITY MODE COMMAND 

This message is sent by the CN to trigger the integrity and ciphering functions over the radio interface. 

Direction: CN -^ RNC. 

Signalling bearer mode: Connection oriented. 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



74 



ETSI TS 125 413 V4.10.0 (2003-09) 



IE/Group Name 


Presence 


Range 


IE type and 
reference 


Semantics 
description 


Criticality 


Assigned 
Criticality 


Message Type 


M 




9.2.1.1 




YES 


reject 


Integrity Protection 
Information 


M 




9.2.1.11 


Integrity 
information 
includes 
key and 
permitted 
algorithms. 


YES 


reject 


Encryption Information 







9.2.1.12 


Encryption 
information 
includes 
key and 
permitted 
algorithms. 


YES 


ignore 


Key Status 


M 




9.2.1.36 




YES 


reject 



9.1 .27 SECURITY MODE COMPLETE 

This message is sent by the RNC as a successful response to SECURITY MODE COMMAND message. 

Direction: RNC -^ CN. 

SignalHng bearer mode: Connection oriented. 



IE/Group Name 


Presence 


Range 


IE type and 
reference 


Semantics 
description 


Criticality 


Assigned 
Criticality 


Message Type 


M 




9.2.1.1 




YES 


reject 


Chosen Integrity Protection 
Algorithm 


M 




9.2.1.13 




YES 


reject 


Chosen Encryption 
Algorithm 







9.2.1.14 




YES 


ignore 


Criticality Diagnostics 







9.2.1.35 




YES 


ignore 



9.1 .28 SECURITY MODE REJECT 

This message is sent by the RNC as a unsuccessful response to SECURITY MODE COMMAND message. 

Direction: RNC -^ CN. 

Signalling bearer mode: Connection oriented. 



IE/Group Name 


Presence 


Range 


IE type and 
reference 


Semantics 
description 


Criticality 


Assigned 
Criticality 


Message Type 


M 




9.2.1.1 




YES 


reject 


Cause 


M 




9.2.1.4 




YES 


ignore 


Criticality Diagnostics 







9.2.1.35 




YES 


ignore 



9.1 .29 LOCATION REPORTING CONTROL 

This message is sent by the CN to initiate, modify or stop location reporting from the RNC to the CN. 

Direction: CN -^ RNC. 

Signalling bearer mode: Connection oriented. 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



75 



ETSI TS 125 413 V4.10.0 (2003-09) 



IE/Group Name 


Presence 


Range 


IE type and 
reference 


Semantics 
description 


Criticality 


Assigned 
Criticality 


Message Type 


M 




9.2.1.1 




YES 


ignore 


Request Type 


M 




9.2.1.16 




YES 


ignore 


Vertical Accuracy Code 







9.2.1.46a 




YES 


Ignore 


Response Time 







9.2.1.46b 




YES 


Ignore 


Positioning Priority 







9.2.1.46c 




YES 


Ignore 


Client Type 







9.2.1. 46d 




YES 


ignore 



9.1 .30 LOCATION REPORT 

This message is sent by the RNC to the CN with information about the UE location. 

Direction: RNC -^ CN. 

Signalling bearer mode: Connection oriented. 



IE/Group Name 


Presence 


Range 


IE type and 
reference 


Semantics 
description 


Criticality 


Assigned 
Criticality 


IVIessage Type 


M 




9.2.1.1 




YES 


ignore 


Area Identity 







9.2.3.10 




YES 


ignore 


Cause 







9.2.1.4 




YES 


ignore 


Request Type 







9.2.1.16 




YES 


ignore 


Last Known Service Area 







9.2.3.22 




YES 


ignore 



9.1 .31 DATA VOLUME REPORT REQUEST 

This message is sent by the CN to request unsuccessfully transmitted data volumes for specific RABs. 

Direction: CN -^ RNC. 

Signalling bearer mode: Connection oriented. 



IE/Group Name 


Presence 


Range 


IE type and 
reference 


Semantics 
description 


Criticality 


Assigned 
Criticality 


IVIessage Type 


M 




9.2.1.1 




YES 


reject 


RABs Data Volume Report 
List 


M 








YES 


ignore 


>RABs Data Volume 
Report Item lEs 




1 to 
<maxnoofRABs> 






EACH 


reject 


»RAB ID 


M 




9.2.1.2 




- 





Range bound 


Explanation 


maxnoofRABs 


IVIaximum no. of RABs for one UE. Value is 256. 



9.1 .32 DATA VOLUME REPORT 

This message is sent by the RNC and informs the CN about unsuccessfully transmitted data volumes for requested 
RABs. 

Direction: RNC -^ CN. 

Signalling bearer mode: Connection oriented. 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



76 



ETSI TS 125 413 V4.10.0 (2003-09) 



IE/Group Name 


Presence 


Range 


IE type and 
reference 


Semantics 
description 


Criticality 


Assigned 
Criticality 


Message Type 


M 




9.2.1.1 




YES 


reject 


RABs Data Volume Report 
List 











YES 


ignore 


>RABs Data Volume 
Report Item IBs 




1 to 
<maxnoofRABs> 






EACH 


ignore 


»RAB ID 


M 




9.2.1.2 




- 




»RAB Data 
Volume Report List 











- 




»>RAB Data 
Volume Report 
Item lEs 




1 to 
<maxnoofVol> 










»»Unsuccessf 
ully Transmitted 
DL Data Volume 


M 




9.2.3.12 








»»Data 

Volume 

Reference 







9.2.3.13 








RABs Failed To Report 
List 











YES 


ignore 


>RABs Failed To Report 
Item lEs 




1 to 
<maxnoofRABs> 






EACH 


ignore 


»RAB ID 


M 




9.2.1.2 




- 




»Cause 


M 




9.2.1.4 




- 




Criticality Diagnostics 







9.2.1.35 




YES 


ignore 


















Range bound 


Explanation 






maxnoofRABs 


Maximum no. 


of RABs for one UE. Value is 256. 








maxnoofVol 


Maximum no. 


of reported data volume for one RAB. Value is 2 


) 





9.1 .33 INITIAL UE MESSAGE 

This message is sent by the RNC to transfer the radio interface initial layer 3 message to the CN. 

Direction: RNC -^ CN. 

Signalling bearer mode: Connection oriented. 



IE/Group Name 


Presence 


Range 


IE type and 
reference 


Semantics 
description 


Criticality 


Assigned 
Criticality 


Message Type 


M 




9.2.1.1 




YES 


ignore 


CN Domain Indicator 


M 




9.2.1.5 




YES 


ignore 


LAI 


M 




9.2.3.6 




YES 


ignore 


RAC 


C - ifPS 




9.2.3.7 




YES 


ignore 


SAI 


M 




9.2.3.9 




YES 


ignore 


NAS-PDU 


M 




9.2.3.5 




YES 


ignore 


lu Signalling Connection 
Identifier 


M 




9.2.1.38 




YES 


ignore 


Global RNC-ID 


M 




9.2.1.39 




YES 


ignore 



Condition 


Explanation 


ifPS 


This IE shall be present if the CN Domain Indicator \E is set to "PS 
domain". 



9.1.34 DIRECT TRANSFER 

This message is sent by both the CN and the RNC and is used for carrying NAS information over the lu interface. 
Direction: RNC -^ CN and CN -^ RNC. 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



77 



ETSI TS 125 413 V4.10.0 (2003-09) 



Signalling bearer mode: Connection oriented. 



IE/Group Name 


Presence 


Range 


IE type and 
reference 


Semantics 
description 


Criticality 


Assigned 
Criticality 


Message Type 


M 




9.2.1.1 




YES 


ignore 


NAS-PDU 


M 




9.2.3.5 




YES 


ignore 


LAI 







9.2.3.6 




YES 


ignore 


RAG 







9.2.3.7 




YES 


ignore 


SAI 







9.2.3.9 




YES 


ignore 


SARI 







9.2.3.8 




YES 


ignore 



9.1 .35 CN INFORMATION BROADCAST REQUEST 

Void. 

9.1 .36 CN INFORMATION BROADCAST CONFIRM 

Void. 

9.1 .37 CN INFORMATION BROADCAST REJECT 

Void. 

9.1.38 OVERLOAD 

This message is sent by both the CN and the RNC to indicate that the node is overloaded. 
Direction: RNC -^ CN and CN -^ RNC. 
Signalling bearer mode: Connectionless. 



IE/Group Name 


Presence 


Range 


IE type and 
reference 


Semantics 
description 


Criticality 


Assigned 
Criticality 


IVIessage Type 


M 




9.2.1.1 




YES 


ignore 


Number Of Steps 







9.2.1.32 




YES 


ignore 


Global RNC-ID 







9.2.1.39 




YES 


ignore 


CN Domain Indicator 







9.2.1.5 




YES 


ignore 



9.1.39 RESET 

This message is sent by both the CN and the RNC and is used to request that the other node shall be reset. 
Direction: RNC -^ CN and CN -^ RNC. 
Signalling bearer mode: Connectionless. 



IE/Group Name 


Presence 


Range 


IE type and 
reference 


Semantics 
description 


Criticality 


Assigned 
Criticality 


Message Type 


M 




9.2.1.1 




YES 


reject 


Cause 


M 




9.2.1.4 




YES 


ignore 


ON Domain Indicator 


M 




9.2.1.5 




YES 


reject 


Global RNC-ID 







9.2.1.39 




YES 


ignore 


Global CN-ID 







9.2.1.46 




YES 


ignore 



9.1 .40 RESET ACKNOWLEDGE 

This message is sent by both the CN and the RNC as a response to RESET message. 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 

Direction: RNC -^ CN and CN -^ RNC. 
Signalling bearer mode: Connectionless. 



78 



ETSI TS 125 413 V4.10.0 (2003-09) 



IE/Group Name 


Presence 


Range 


IE type and 
reference 


Semantics 
description 


Criticality 


Assigned 
Criticality 


Message Type 


M 




9.2.1.1 




YES 


reject 


CN Domain Indicator 


M 




9.2.1.5 




YES 


reject 


Criticality Diagnostics 







9.2.1.35 




YES 


ignore 


Global RNC-ID 







9.2.1.39 




YES 


ignore 


Global CN-ID 







9.2.1.46 




YES 


ignore 



9.1.41 ERROR INDICATION 

This message is sent by both the CN and the RNC and is used to indicate that some error has been detected in the node. 

Direction: RNC -^ CN and CN -^ RNC. 

Signalling bearer mode: Connection oriented or connectionless. 



IE/Group Name 


Presence 


Range 


IE type and 
reference 


Semantics 
description 


Criticality 


Assigned 
Criticality 


IVIessage Type 


M 




9.2.1.1 




YES 


ignore 


Cause 







9.2.1.4 




YES 


ignore 


Criticality Diagnostics 







9.2.1.35 




YES 


ignore 


CN Domain Indicator 







9.2.1.5 




YES 


ignore 


Global RNC-ID 







9.2.1.39 




YES 


ignore 


Global CN-ID 







9.2.1.46 




YES 


ignore 



9.1 .42 CN DEACTIVATE TRACE 

This message is sent by the CN to request the RNC to stop producing a trace record for the indicated trace reference. 

Direction: CN ^ RNC. 

Signalling bearer mode: Connection Oriented. 



IE/Group Name 


Presence 


Range 


IE type and 
reference 


Semantics 
description 


Criticality 


Assigned 
Criticality 


IVIessage Type 


M 




9.2.1.1 




YES 


ignore 


Trace Reference 


M 




9.2.1.8 




YES 


ignore 


Trigger ID 







9.2.1.7 




YES 


ignore 



9.1 .43 RANAP RELOCATION INFORMATION 

This message is part of a special RANAP Relocation Information procedure, and is sent between RNCs during 
Relocation. 

Direction: RNC - RNC. 

Signalling bearer mode: Not applicable. 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



79 



ETSI TS 125 413 V4.10.0 (2003-09) 



IE/Group Name 


Presence 


Range 


IE type and 
reference 


Semantics 
description 


Criticality 


Assigned 
Criticality 


Message Type 


M 




9.2.1.1 




YES 


ignore 


Direct Transfer 
Information List 











YES 


ignore 


>Direct Transfer 
Information Item lEs 




1 to <maxnoofDT> 




Information 
received in 
one or more 
DIRECT 
TRANSFER 
messages 
and that 
needs to be 
transferred 
to target 
RNC for 
further 
transmissio 
ntotheUE. 


EACH 


ignore 


»NAS-PDU 


M 




9.2.3.5 




- 




»SAPI 


M 




9.2.3.8 




- 




»CN Domain 
Indicator 


M 




9.2.1.5 




- 




RAB Contexts List 











YES 


ignore 


>RAB Contexts Item lEs 




1 to 
<maxnoofRABs> 






EACH 


ignore 


»RAB ID 


M 




9.2.1.2 




- 




»DLGTP-PDU 
Sequence Number 







9.2.2.3 




- 




»ULGTP-PDU 
Sequence Number 







9.2.2.4 




- 




»DLN-PDU 
Sequence Number 







9.2.1.33 




- 




»ULN-PDU 
Sequence Number 







9.2.1.34 




- 





Range bound 


Explanation 


maxnoofDT 


Maximum no. of DT information. Value is 15. 


maxnoofRABs 


Maximum no. of RABs for one UE. Value is 256. 



9.1.44 RESET RESOURCE 

This message is sent by either CN or RNC. The sending entity informs the receiving entity that the sending requests the 
receiving entity to release resources and references associated to lu signalHng connection identifiers in the message. 

Direction: CN <-^ RNC. 

SignalHng bearer mode: Connectionless. 



IE/Group Name 


Presence 


Range 


IE type and 
reference 


Semantics 
description 


Criticality 


Assigned 
Criticality 


Message Type 


M 




9.2.1.1 




YES 


reject 


CN Domain Indicator 


M 




9.2.1.5 




YES 


reject 


Cause 


M 




9.2.1.4 




YES 


ignore 


Reset Resource List 


M 








YES 


ignore 


>Reset Resource Item 
IBs 




1 to 

<maxnoofluSigCo 

nlds> 






EACH 


reject 


»lu Signalling 
Connection Identifier 


M 




9.2.1.38 




- 




Global RNC-ID 







9.2.1.39 




YES 


ignore 


Global CN-ID 







9.2.1.46 




YES 


ignore 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



80 



ETSI TS 125 413 V4.10.0 (2003-09) 



Range bound 


Explanation 


maxnoofluSigConlds 


Maximum no. of lu signalling connection identifiers. Value is 250. 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



81 



ETSI TS 125 413 V4.10.0 (2003-09) 



9.1 .45 RESET RESOURCE ACKNOWLEDGE 

This message is sent by either the CN or RNC inform the CN or RNC that the RESET RESOURCE message has been 
received. 

Direction: CN <-^ RNC. 

SignalHng bearer mode: Connectionless. 



IE/Group Name 


Presence 


Range 


IE type and 
reference 


Semantics 
description 


Criticality 


Assigned 
Criticality 


IVIessage Type 


M 




9.2.1.1 




YES 


reject 


CN Domain Indicator 


M 




9.2.1.5 




YES 


reject 


Reset Resource List 


M 








YES 


ignore 


>Reset Resource 
Item lEs 




1 to 

<maxnoofluSigCo 

nlds> 




This list 
shall be in 
the same 
order as the 
list received 
in the 
RESET 
RESOURC 
E message. 


EACH 


reject 


»lu Signalling 

Connection 

Identifier 


M 




9.2.1.38 








Global RNC-ID 







9.2.1.39 




YES 


ignore 


Criticality Diagnostics 







9.2.1.35 




YES 


ignore 


Global CN-ID 







9.2.1.46 




YES 


ignore 



Range bound 


Explanation 


maxnoofluSigConlds 


IVIaximum no. of lu signalling connection identifiers. Value is 250. 



9.1 .46 RAB MODIFY REQUEST 

This message is sent by the RNC to the CN to request modification of one or more RABs for the same UE. 

Direction: RNC -^ CN. 

Signalling bearer mode: Connection oriented. 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



82 



ETSI TS 125 413 V4.10.0 (2003-09) 



IE/Group Name 


Presence 


Range 


IE type and 
reference 


Semantics 
description 


Criticality 


Assigned 
Criticality 


Message Type 


M 




9.2.1.1 




YES 


Ignore 


RABs To Be Modified List 


M 








YES 


Ignore 


>RABs To Be Modified 
Item lEs 




1 to 
<maxnoofRABs> 






EACH 


Ignore 


»RAB ID 


M 




9.2.1.2 


Uniquely 
identifies the 
RAB for a 
specific CN 
domain, for a 
particular UE. 






» Requested RAB 
Parameter Values 


M 




9.2.1.45 


Includes RAB 
parameters for 
which different 
values than 
what was 
originally 
negotiated are 
being 
requested. 







Range bound 


Explanation 


maxnoofRABs 


Maximum no. of RABs for one UE. Value is 256. 



9.1 .47 LOCATION RELATED DATA REQUEST 

This message is sent by the CN either to initiate deHvery of dedicated assistance data from the RNC to the UE, or to 
retrieve deciphering keys for the broadcasted assistance data. 

Direction: CN -^ RNC. 

Signalling bearer mode: Connection oriented. 



IE/Group Name 


Presence 


Range 


IE type and 
reference 


Semantics 
description 


Criticality 


Assigned 
Criticality 


Message Type 


M 




9.2.1.1 




YES 


reject 


Location Related Data 
Request Type 


M 




9.2.3.19 




YES 


reject 



9.1 .48 LOCATION RELATED DATA RESPONSE 

This message is sent by the RNC to report the successful response of the LOCATION RELATED DATA REQUEST 

message. 

Direction: RNC -^ CN. 

Signalling bearer mode: Connection oriented. 



IE/Group Name 


Presence 


Range 


IE type and 
reference 


Semantics 
description 


Criticality 


Assigned 
Criticality 


Message Type 


M 




9.2.1.1 




YES 


reject 


Broadcast Assistance Data 
Deciphering Keys 







9.2.3.20 




YES 


ignore 



9.1 .49 LOCATION RELATED DATA FAILURE 

This message is sent by the RNC to report the unsuccessful response of the LOCATION RELATED DATA REQUEST 

message. 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



83 



ETSI TS 125 413 V4.10.0 (2003-09) 



Direction: RNC -^ CN. 

Signalling bearer mode: Connection oriented. 



IE/Group Name 


Presence 


Range 


IE type and 
reference 


Semantics 
description 


Criticality 


Assigned 
Criticality 


Message Type 


M 




9.2.1.1 




YES 


reject 


Cause 


M 




9.2.1.4 




YES 


ignore 



9.2 



Information Element Definitions 



9.2.0 General 

Subclause 9.2 presents the RANAP IE definitions in tabular format. The corresponding ASN.l definition is presented in 
subclause 9.3. In case there is contradiction between the tabular format in subclause 9.2 and the ASN.l definition, the 
ASN.l shall take precedence, except for the definition of conditions for the presence of conditional elements, where the 
tabular format shall take precedence. 

When specifying information elements which are to be represented by bitstrings, if not otherwise specifically stated in 
the semantics description of the concerned IE or elsewhere, the following principle applies with regards to the ordering 
of bits: 

The first bit (leftmost bit) contains the most significant bit (MSB); 

The last bit (rightmost bit) contains the least significant bit (LSB); 

When importing bitstrings from other specifications, the first bit of the bitstring contains the first bit of the 
concerned information; 

9.2.1 Radio Network Layer Related lEs 
9.2.1.1 Message Type 

Message Type IE uniquely identifies the message being sent. It is mandatory for all messages. 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



84 



ETSI TS 125 413 V4.10.0 (2003-09) 



IE/Group Name 



Presence 



Range 



IE type and reference 



Semantics description 



Message Type 



Assumed max no of messages 
is 256. 



>Procedure Code 



M 



(RAB Assignment, 

RAB Release Request, 

lu Release Request, 

lu Release, 

Relocation Preparation, 

Relocation Resource 

Allocation, 

Relocation Detect, 

Relocation Complete 

Relocation Cancel, 

SRNS Context 

Transfer, 

SRNS Data Forwarding 

Initiation, 

SRNS Context 

Forwarding from 

Source RNC to CN, 

SRNS Context 

Forwarding to Target 

RNC from CN, 

Paging, 

Common ID, 

CN Invoke Trace, 

Security Mode Control, 

Location Reporting 

Control 

Location Report, 

Data Volume Report, 

Initial UE IVIessage 

Direct Transfer, 

Overload Control, 

Reset, 

Error Indication, 

CN Deactivate Trace, 

RANAP Relocation 

Information, 

Reset Resource, 

RAB Modify Request, 
Location Related Data) 



>Type of Message 



M 



CHOICE 

(Initiating Message, 
Successful Outcome, 
Unsuccessful Outcome, 
Outcome, ...) 



9.2.1.2 



RAB ID 



This element uniquely identifies the radio access bearer for a specific CN domain for a particular UE, which makes the 
RAB ID unique over one lu connection. The RAB ID shall remain the same for the duration of the RAB even when the 
RAB is relocated to another lu connection. 

The purpose of the element is to bind data stream from the Non- Access Stratum point of view (e.g. bearer of call or 
PDF context) and radio access bearer in Access Stratum. The value is also used in the RNC to relate Radio Bearers to a 
RAB. The content of this information element is transferred unchanged from the CN node (i.e., MSC or SGSN) via 
RNC to UE by RANAP messages and RRC messages. For RRC messages refer to [10]. 

The element contains binary representation of either the Stream Identifier (SI) for CS domain or the Network Service 
Access Point Identifier (NSAPI) for PS domain. These identifiers are coded in the RAB ID element in accordance with 
the coding of the Stream Identifier IE and with the coding of the NSAPI IE in [8]. 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



85 



ETSI TS 125 413 V4.10.0 (2003-09) 



IE/Group Name 


Presence 


Range 


IE type and 
reference 


Semantics description 


RABID 


M 




BIT STRING 

(8) 





9.2.1.3 



RAB Parameters 



The purpose of the RAB parameters IE group and other parameters within the RAB parameters IE group is to indicate 
all RAB attributes as defined in [7] for both directions. 



IE/Group Name 


Presence 


Range 


IE type and 
reference 


Semantics description 


RAB parameters 










>Traffic Class 


M 




ENUMERATED 
(conversational, 
streaming, 
interactive, 
background, ...) 


Desc: This IE indicates the type 
of application for which the 
Radio Access Bearer service is 
optimised 


>RAB Asymmetry 
Indicator 


M 




ENUMERATED 

(Symmetric 

bidirectional, 

Asymmetric Uni 

directional 

downlink. 

Asymmetric Uni 

directional 

Uplink, 

Asymmetric 

Bidirectional, ...) 


Desc: This IE indicates 
asymmetry or symmetry of the 
RAB and traffic direction 


>Maximum Bit Rate 


M 


1 to <nbr- 

SeparateTrafficDIr 

ections> 


INTEGER 
(1.. 16,000,000) 


Desc: This IE indicates the 
maximum number of bits 
delivered by UTRAN and to 
UTRAN at a SAP within a period 
of time, divided by the duration 
of the period. 
The unit is: bit/s 
Usage: 
When nbr- 

SeparateTrafficDirections is 
equal to 2, then Maximum Bit 
Rate attribute for downlink is 
signalled first, then Maximum Bit 
Rate attribute for uplink 


>Guaranteed Bit Rate 


0- 

iftrafficCon 
v-Stream 


to <nbr- 

SeparateTrafficDIr 

ections> 


INTEGER 
(0.. 16,000,000) 


Desc: This IE indicates the 
guaranteed number of bits 
delivered at a SAP within a 
period of time (provided that 
there is data to deliver), divided 
by the duration of the period. 
The unit is: bit/s 
Usage: 

1. When nbr- 
SeparateTrafficDirections is 
equal to 2, then 
Guaranteed Bit Rate for 
downlink is signalled first, 
then Guaranteed Bit Rate 
for uplink 

2. Delay and reliability 
attributes only apply up to 
the guaranteed bit rate 

3. Conditional valuefor the 
case of Support Mode for 
pre-defined SOU sizes: 
Set to highest not rate 
controllable bitrate, where 
bitrate is either 

- one of the RAB subflow 
combination bitrate lEs 
(when present) 

or 

- one of the calculated 
values given when dividing 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



86 



ETSI TS 125 413 V4.10.0 (2003-09) 



IE/Group Name 


Presence 


Range 


IE type and 
reference 


Semantics description 


RAB parameters 


















the compound Subflow 
combination SDU sizes by 
the value of the IE 
Maximum SDU Size and 
then multiplying this result 
by the value of the IE 
Maximum Bit Rate. 


>Delivery Order 


M 




ENUMERATED 
(delivery order 
requested, 
delivery order 
not requested) 


Desc: This IE indicates whether 
the RAB shall provide in- 
sequence SDU delivery or not 
Usage: 

Delivery order requested: in 
sequence delivery shall be 
guaranteed by UTRAN on all 
RAB SDUs 

Delivery order not requested: in 
sequence delivery is not 
required from UTRAN 


>Maximum SDU Size 


M 




INTEGER 
(0..32768) 


Desc: This IE indicates the 

maximum allowed SDU size 

The unit is: bit. 

Usage: 

Conditional value: 

Set to largest RAB Subflow 

Combination compound SDU 

size (when present) among the 

different RAB Subflow 

Combinations 


>SDU parameters 




1 to 

<maxRABSubflow 

s> 


See below 


Desc: This IE contains the 

parameters characterizing the 

RAB SDUs 

Usage 

Given per subflow with first 

occurence corresponding to 

subflow#1 etc... 


>Transfer Delay 


C- 

iftrafficCon 
v-Stream 




INTEGER 
(0..65535) 


Desc: This IE indicates the 
maximum delay for 95th 
percentile of the distribution of 
delay for all delivered SDUs 
during the lifetime of a RAB, 
where delay for an SDU is 
defined as the time from a 
request to transfer an SDU at 
one SAP to its delivery at the 
other SAP 

The unit is: millisecond. 
Usage: 


>Trafflc Handling Priority 


C- 

iftrafficlnter 

activ 




INTEGER 
{spare (0), 
highest (1), .., 
lowest (14), no 
priority (15)} 
(0..15) 


Desc: This IE specifies the 
relative importance for handling 
of all SDUs belonging to the 
radio access bearer compared 
to the SDUs of other bearers 
Usages 

Values between 1 and 14 are 
ordered in decreasing order of 
priority, '1' being the highest and 
'14' the lowest. 
Value shall be treated as a 
logical error if received. 


>Allocation/Retention 
priority 







See below 


Desc: This IE specifies the 
relative importance compared to 
other Radio access bearers for 
allocation and retention of the 
Radio access bearer. 
Usage: 

If this IE is not received, the 
request is regarded as it cannot 
trigger the pre-emption process 
and it is vulnerable to the pre- 
emption process. 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



87 



ETSI TS 125 413 V4.10.0 (2003-09) 



IE/Group Name 


Presence 


Range 


IE type and 
reference 


Semantics description 


RAB parameters 










>Source Statistics 
Descriptor 


C- 

iftrafficCon 
v-Stream 




ENUMERATED 
(speech, 
unknown, ...) 


Desc: This IE_specifies 
characteristics of the source of 
submitted SDUs 
Usages 


>Relocation 
Requirement 







ENUMERATED 
(lossless, none, 
..., realtime) 


This IE shall be present for 
RABs towards the PS domain, 
otherwise it shall not be present. 
Desc: This lEJs no longer used. 
Usagei 

It shall always be set to "none" 
when sent and it shall always be 
ignored when received. 



Range Bound 


Explanation 


nbr-SeparatelrafficDirection 


Number of Traffic Directions being signalled 

separately. 

Set to 2 if RAB asymmetry indicator is 

asymmetric bidirectional. 

Set to 1 in all otiier cases. 



Range Bound 


Explanation 


maxRABSubflows 


IVIaximum number of Subflows per RAB. Value 
is 7 



Condition 


Explanation 


IftrafficConv-Stream 


Tills IE sliall be present if tlie Traffic Class IE is set to 
"Conversational" or "Streaming" 


Iftrafficlnteractiv 


Tills IE sliall be present if ttie Traffic Class IE is set to "Interactive" 



IE/Group Name 


Presence 


Range 


IE type and 
reference 


Semantics description 


SDU parameters 










> SDU Error Ratio 


C- 

ifErroneou 
sSDU 






Desc: This IE indicates the 

fraction of SDUs lost or detected 

as erroneous. 

This is a Reliability attribute 

Usage: 

The attribute is coded as follows: 

Mantissa* 10 -'''"■°"'="' 


»Mantissa 


M 




INTEGER (1 ..9) 




»Exponent 


M 




INTEGER (1 ..6) 




>Residual Bit Error 
Ratio 


M 






Desc: This IE indicates the 

undetected bit error ratio for 

each subflow in the delivered 

SDU. 

This is a Reliability attribute. 

Usage: 

The attribute is coded as follows: 

Mantissa* 10-""'°"''"' 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



88 



ETSI TS 125 413 V4.10.0 (2003-09) 



»Mantissa 


M 




INTEGER (1 ..9) 




»Exponent 


M 




INTEGER (1 ..8) 




>Delivery Of Erroneous 
SDU 


M 




ENUMERATED 
(yes, no, no- 
error-detection- 
consideration) 


Desc: This IE indicates whether 
SDUs with detected errors shall 
be delivered or not. In case of 
unequal error protection, the 
attribute is set per subflow 
This is a Reliability attribute 
Usage: 

Yes: error detection applied, 
erroneous SDU delivered 
No. Error detection is applied , 
erroneous SDU discarded 
no-error-detection-consideration: 
SDUs delivered without 
considering error detection. 
If the RNC receives this IE set to 
'Yes' and the User Plane Mode 
IE is set to 'transparent mode', it 
should consider it as 'no-error- 
detection-consideration'. 


>SDU format 
information Parameter 





1 to 

<maxRABSubflow 

Combinations> 


See below 


Desc: This IE contains the list 
of possible exact sizes of SDUs 
and/or RAB Subflow 
Combination bit rates. 
Given per RAB Subflow 
Combination with first occurence 
corresponding to RAB Subflow 
Combination number 1 . 
It shall always be present for 
rate controllable RABs. 



Range Bound 


Explanation 


maxRABSubflowCombinations 


Maximum number of RAB Subflow 
Combinations. Value is 64. 



Condition 


Explanation 


IfErroneousSDU 


This IE shall be present if the Delivery Of Erroneous SDU IE is set 
to "Yes" or "No". 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



89 



ETSI TS 125 413 V4.10.0 (2003-09) 



IE/Group Name 


Presence 


Range 


IE type and 
reference 


Semantics description 


SDU Format Information 
Parameter 








At least one of the Subflow SDU 
size IE and the RAB Subflow 
Combination bit rate IE shall be 
present when SDU format 
information Parameter \E is 
present. 

For the case subflow SDUs are 
transmitted at constant time 
interval, only one of the two lEs 
shall be present. 


>Subflow SDU Size 







INTEGER 
(0..4095) 


Desc: This IE indicates the exact 
size of the SDU. 
The unit is: bit. 
Usage: 

This IE is only used for RABs that 
have predefined SDU size(s). It 
shall be present for RABs having 
more than one subflow. 
For RABs having only one 
subflow, this IE shall be present 
only when the RAB is rate 
controllable and the SDU size of 
some RAB Subflow 
Combination(s) is different than 
the IE Maximum SDU Size. 
When this IE is not present and 
SDU format information Parameter 
is present, then the Subflow SDU 
size for the only existing subflow 
takes the value of the IE Maximum 
SDU size. 


>RAB Subflow 
Combination Bit Rate 







INTEGER 
(0.. 16,000,000 
) 


Desc: This IE indicates the RAB 
Subflow Combination bit rate. 
The unit is: bit/s. 
Usage: 

When this IE is not present and 
SDU format information parameter 
is present then all Subflow SDUs 
are transmitted (when there is data 
to be transmitted) at a constant 
time interval. 

The value of this IE shall not 
exceed the maximum value of the 
lEs 'Maximum Bit Rate'. 
The value of RAB Subflow 
Combination bitrate indicates that 
the RAB uses discontinuous 
transfer of the SDUs. 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



90 



ETSI TS 125 413 V4.10.0 (2003-09) 



IE/Group Name 


Presence 


Range 


IE type and 
reference 


Semantics description 


Allocation/Retention 
Priority 










>Priority Level 


M 




INTEGER 
{spare (0), 
highest (1), .., 
lowest (14), no 
priority (15)} 
(0..15) 


Desc: This IE indicates the 
phohty of the request. 
Usage: 

Values between 1 and 14 are 
ordered in decreasing order of 
phohty, '1' being the highest and 
'14' the lowest. 
Value shall be treated as a 
logical error if received. 
The priority level and the 
preemption indicators may be 
used to determine whether the 
request has to be performed 
unconditionally and immediately 


>Pre-emption Capability 


M 




ENUMERATE 
D(shall not 
trigger pre- 
emption, may 
trigger pre- 
emption) 


Descr.: This IE indicates the pre- 
emption capability of the request 
on other RABs 
Usage: 

The RAB shall not pre-empt other 
RABs or, the RAB may pre-empt 
other RABs 

The Pre-emption Capability 
indicator applies to the allocation 
of resources for a RAB and as 
such it provides the trigger to the 
pre-emption procedures/processes 
of the RNS. 


>Pre-emption 
Vulnerability 


M 




ENUMERATE 
D(not pre- 
emptable, 
pre-emptable) 


Desc: This IE indicates the 
vulnerability of the RAB to 
preemption of other RABs. 
Usage: 

The RAB shall not be pre-empted 
by other RABs or the RAB may be 
pre-empted by other RABs. 
Pre-emption Vulnerability indicator 
applies for the entire duration of 
the RAB, unless modified and as 
such indicates whether the RAB is 
a target of the pre-emption 
procedures/processes of the RNS 


>Queuing Allowed 


M 




ENUMERATE 
D(queuing not 
allowed, 
queuing 
allowed) 


Desc: This IE indicates whether 
the request can be placed into a 
resource allocation queue or not. 
Usage: 

Queuing of the RAB is allowed 
Queuing of the RAB is not allowed 
Queuing allowed indicator applies 
for the entire duration of the RAB, 
unless modified. 



9.2.1.4 Cause 

The purpose of the Cause IE is to indicate the reason for a particular event for the RANAP protocol. 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



91 



ETSI TS 125 413 V4.10.0 (2003-09) 



IE/Group Name 



Presence 



Range 



IE type and 
reference 



Semantics description 



Choice Cause 



>Radio Network Layer 
Cause 



INTEGER 
(RAB pre- 
empted(1), 

Trelocoverall 
Expiry(2), 

Trelocprep 
Expiry(3), 

Treloccomplete 
Expiry(4), 

Tqueing Expiry(5), 

Relocation 
Triggered(6), 

Unable to 
Establish During 
Relocation{8), 

Unknown Target 
RNC{9), 

Relocation 
Cancelled{10), 

Successful 
Relocation{11), 

Requested 
Ciphering and/or 
Integrity 
Protection 
Algorithms not 
Supported(12), 

Conflict with 
already existing 
Integrity protection 
and/or Ciphering 
information (13), 

Failure in the 
Radio Interface 
Procedure{14), 

Release due to 
UTRAN 
Generated 
Reason(15), 

User 
lnactivity(16), 

Time Critical 
Relocation{17), 

Requested Traffic 
Class not 
Available{18), 

Invalid RAB 
Parameters 
Value{19), 

Requested 



Value range is 1 - 64. 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



92 



ETSI TS 125 413 V4.10.0 (2003-09) 



IE/Group Name 



Presence 



Range 



IE type and 
reference 



Semantics description 



Choice Cause 



Maximum Bit Rate 
not Available(20), 

Requested 
IVIaximum Bit Rate 
for DL not 
Available{33), 

Requested 
IVIaximum Bit Rate 
for UL not 
Available{34), 

Requested 
Guaranteed Bit 
Rate not 
Available{21), 

Requested 
Guaranteed Bit 
Rate for DL not 
Available{35), 

Requested 
Guaranteed Bit 
Rate for UL not 
Available{36), 

Requested 
Transfer Delay not 
Achievable(22), 

Invalid RAB 
Parameters 
Combination(23), 

Condition 
Violation for SDU 
Parameters(24), 

Condition 
Violation for 
Traffic Handling 
Priority(25), 

Condition 
Violation for 
Guaranteed Bit 
Rate(26), 

User Plane 
Versions not 
Supported(27), 

lu UP Failure(28), 

TRELOCalloc 

Expiry (7), 

Relocation Failure 
in Target CN/RNC 
or Target System 
(29), 

Invalid RAB 
ID(30), 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



93 



ETSI TS 125 413 V4.10.0 (2003-09) 



IE/Group Name 



Presence 



Range 



IE type and 
reference 



Semantics description 



Choice Cause 



No remaining 
RAB{31), 

Interaction with 

other 

procedure{32), 

Repeated Integrity 

Checking 

Failure(37), 

Requested 
Request Type not 
supported{38), 

Request 
superseded{39), 

Release due to 
UE generated 
signalling 
connection 
release(40), 

Resource 

Optimisation 

Relocation{41), 

Requested 
Information Not 
Available{42), 

Relocation 
desirable for radio 
reasons (43), 

Relocation not 
supported in 
Target RNC or 
Target 

system{44), 

Directed Retry 
(45), 

Radio Connection 
With UE Lost(46), 

RNC unable to 
establish all RFCs 
(47), 

Deciphering Keys 
Not Available(48), 

Dedicated 
Assistance data 
Not Available(49), 

Relocation Target 
not allowed(50), 

Location 
Reporting 

Congestion(51)) 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



94 



ETSI TS 125 413 V4.10.0 (2003-09) 



IE/Group Name 


Presence 


Range 


IE type and 
reference 


Semantics description 


Choice Cause 










>Transport Layer Cause 






INTEGER 

( 

Signalling 

Transport 

Resource 

Failure(65), 

lu Transport 
Connection Failed 
to Establish(66)) 


Value range is 65 - 80. 


>NAS Cause 






INTEGER 
(User Restriction 
Start 
lndication(81). 

User Restriction 

End 

lndication(82). 

Normal 
Release(83)) 


Value range is 81 - 96. 


>Protocol Cause 






INTEGER 
(Transfer Syntax 
Error(97), 

Semantic Error 
(98), 

IVIessage not 
compatible with 
receiver state 
(99), 

Abstract Syntax 
Error (Reject) 
(100), 

Abstract Syntax 
Error (Ignore and 
Notify) (101), 

Abstract Syntax 
Error (Falsely 
Constructed 

Message) (102)) 


Value range is 97- 112. 


>Miscellaneous Cause 






INTEGER 

(O&M 

lntervention(113). 

No Resource 
Available(114), 

Unspecified 
Failure(115), 

Network 
Optimisation(116)) 


Value range is 113-128. 


>Non-standard Cause 






INTEGER 




Value range is 129-256. 
Cause value 256 shall not be 
used. 



The meaning of the different cause values is described in the following table. In general, "not supported" cause values 
indicate that the concerning capability is missing. On the other hand, "not available" cause values indicate that the 
concerning capability is present, but insufficient resources were available to perform the requested action. 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



95 



ETSI TS 125 413 V4.10.0 (2003-09) 



Radio Network Layer cause 


IVIeaning 


Deciphering Keys Not Available 


The action failed because RNC is not able to provide 
requested deciphering keys. 


Conflict with already existing 
Integrity protection and/or Ciphering 
information 


The action was not performed due to that the requested 
security mode configuration was in conflict with the already 
existing security mode configuration. 


Condition Violation For Guaranteed 
Bit Rate 


The action was not performed due to condition violation for 
guaranteed bit rate. 


Condition Violation For SDL) 
Parameters 


The action was not performed due to condition violation for 
SDU parameters. 


Condition Violation For Traffic 
Handling Priority 


The action was not performed due to condition violation for 
traffic handling priority. 


Dedicated Assistance data Not 
Available 


The action failed because RNC is not able to successfully 
deliver the requested dedicated assistance data to the UE. 


Directed Retry 


The reason for action is Directed Retry 


Failure In The Radio Interface 
Procedure 


Radio interface procedure has failed. 


Interaction With Other Procedure 


Relocation was cancelled due to interaction with other 
procedure. 


Invalid RAB ID 


The action failed because the RAB ID is unknown in the RNC. 


Invalid RAB Parameters 
Combination 


The action failed due to invalid RAB parameters combination. 


Invalid RAB Parameters Value 


The action failed due to invalid RAB parameters value. 


lu UP Failure 


The action failed due to lu UP failure. 


No remaining RAB 


The reason for the action is no remaining RAB. 


RAB Pre-empted 


The reason for the action is that RAB is pre-empted. 


Radio Connection With UE Lost 


The action is requested due to losing radio connection to the 
UE 


Release Due To UE Generated 
Signalling Connection Release 


Release requested due to UE generated signalling connection 
release. 


Release Due To UTRAN Generated 
Reason 


Release is initiated due to UTRAN generated reason. 


Relocation Cancelled 


The reason for the action is relocation cancellation. 


Relocation Desirable for Radio 
Reasons 


The reason for requesting relocation is radio related. 


Relocation Failure In Target 
CN/RNC Or Target System 


Relocation failed due to a failure in target CN/RNC or target 
system. 


Relocation Not Supported In Target 
RNC Or Target System 


Relocation failed because relocation was not supported in 
target RNC or target system. 


Relocation Target not allowed 


Relocation to the indicated target cell is not allowed for the UE 
in question. 


Relocation Triggered 


The action failed due to relocation. 


Repeated Integrity Checking Failure 


The action is requested due to repeated failure in integrity 
checking. 


Request Superseded 


The action failed because there was a second request on the 
same RAB. 


Requested Ciphering And/Or 
Integrity Protection Algorithms Not 
Supported 


The UTRAN or the UE is unable to support the requested 
ciphering and/or integrity protection algorithms. 


Requested Guaranteed Bit Rate For 
DL Not Available 


The action failed because requested guaranteed bit rate for 
DL is not available. 


Requested Guaranteed Bit Rate For 
UL Not Available 


The action failed because requested guaranteed bit rate for 
UL is not available. 


Requested Guaranteed Bit Rate Not 
Available 


The action failed because requested guaranteed bit rate is not 
available. 


Requested Information Not 
Available 


The action failed because requested information is not 
available. 


Requested IVIaximum Bit Rate For 
DL Not Available 


The action failed because requested maximum bit rate for DL 
is not available. 


Requested Maximum Bit Rate For 
UL Not Available 


The action failed because requested maximum bit rate for UL 
is not available. 


Requested Maximum Bit Rate Not 
Available 


The action failed because requested maximum bit rate is not 
available. 


Requested Request Type Not 
Supported 


The RNC is not supporting the requested location request 
type either because it doesn't support the requested event or 
it doesn't support the requested report area. 


Location Reporting Congestion 


The action was not performed due to an inability to support 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



96 



ETSI TS 125 413 V4.10.0 (2003-09) 





location reporting caused by overload. 


Requested Traffic Class Not 
Available 


The action failed because requested traffic class is not 
available. 


Requested Transfer Delay Not 
Achievable 


The action failed because requested transfer delay is not 
achievable. 


Resource Optimisation Relocation 


The reason for requesting relocation is resource optimisation. 


Successful Relocation 


The reason for the action is completion of successful 
relocation. 


Time Critical Relocation 


Relocation is requested for time critical reason. 


Tqueuing Expiry 


The action failed due to expiry of the timer Tqueuing. 


TRELOcaiioc Expiry 


Relocation Resource Allocation procedure failed due to expiry 
of the timer TREiocaiioc 


TRELOccompiete Expiry 


The reason for the action is expiry of timer TREioccompiete. 


TRELOcoveraii Expiry 


The reason for the action is expiry of timer TRELOcoveraii- 


TRELOcprep Expiry 


Relocation Preparation procedure is cancelled when timer 
TRELocprep expires. 


Unable To Establish During 
Relocation 


RAB failed to establish during relocation because it cannot be 
supported in the target RNC. 


Unknown Target RNC 


Relocation rejected because the target RNC is not known to 
the CN. 


User Inactivity 


The action is requested due to user inactivity on one or 
several non real time RABs e.g. in order to optimise radio 
resource. 


User Plane Versions Not Supported 


The action failed because requested user plane versions were 
not supported. 


RNC unable to establish all RFCs 


RNC couldn't establish all RAB subflow combinations 
indicated within the RAB Parameters IE. 



Transport Layer cause 


Meaning 


lu Transport Connection Failed to 
Establish 


The action failed because the lu Transport Network Layer 
connection could not be established. 


Signalling Transport Resource 
Failure 


Signalling transport resources have failed (e.g. processor 
reset). 



NAS cause 


IVIeaning 


Normal Release 


The release is normal. 


User Restriction Start Indication 


A location report is generated due to entering a classified area 
set by O&IVI. 


User Restriction End Indication 


A location report is generated due to leaving a classified area 
set by O&M. 



Protocol cause 


Meaning 


Abstract Syntax Error (Reject) 


The received message included an abstract syntax error and 
the concerning criticality indicated "reject". 


Abstract Syntax Error (Ignore And 
Notify) 


The received message included an abstract syntax error and 
the concerning criticality indicated "ignore and notify". 


Abstract Syntax Error (Falsely 
Constructed IVIessage) 


The received message contained lEs or IE groups in wrong 
order or with too many occurrences. 


Message Not Compatible With 
Receiver State 


The received message was not compatible with the receiver 
state. 


Semantic Error 


The received message included a semantic error. 


Transfer Syntax Error 


The received message included a transfer syntax error. 



Miscellaneous cause 


Meaning 


Network Optimisation 


The action is performed for network optimisation. 


No Resource Available 


No requested resource is available. 


O&IVI Intervention 


The action Is due to O&M intervention. 


Unspecified Failure 


Sent when none of the specified cause values applies. 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



97 



ETSI TS 125 413 V4.10.0 (2003-09) 



9.2.1.5 CN Domain Indicator 

Indicates the CN domain from which the message originates or to which the message shall be sent. 



IE/Group Name 


Presence 


Range 


IE type and 
reference 


Semantics description 


CN Domain Indicator 


M 




ENUMERATED (CS 
domain, PS domain) 





9.2.1.6 Trace Type 

Indicates the type of trace information to be recorded. 



IE/Group Name 


Presence 


Range 


IE type and 
reference 


Semantics description 


Trace Type 


M 




OCTET 
STRING (1) 


Coded as the Trace Type 
specified in 3GPP TS based 
on [12]. 



9.2.1.7 Trigger ID 

Indicates the identity of the entity which initiated the trace. 



IE/Group Name 


Presence 


Range 


IE type and 
reference 


Semantics description 


Trigger ID 


M 




OCTET 

STRING 

(3..22) 


Typically an OIVIC identity. 



Note: Due to inconsistency in the definition of Trigger ID between TS 25.413 and [24], it shall be ensured that the 
Trigger ID IE is coded with at least the minimum number of octets required. 

9.2.1.8 Trace Reference 

Provides a trace reference number allocated by the triggering entity. 



IE/Group Name 


Presence 


Range 


IE type and 
reference 


Semantics description 


Trace Reference 


M 




OCTET 

STRING 

(2..3) 





NOTE: Due to inconsistency in the definition of Trace Reference between TS 25.413 and [24], it shall be ensured 
that the Trace Reference IE is coded with at least the minimum number of octets required. 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



98 



ETSI TS 125 413 V4.10.0 (2003-09) 



9.2.1.9 UE Identity 

This element identifies the element to be traced i.e. the subscriber or the user equipment. 



IE/Group Name 


Presence 


Range 


IE type and 
reference 


Semantics description 


Choice UE Identity 










>IMSI 






OCTET 
STRING 
(SIZE (3.. 8)) 


- digits to 9, encoded 0000 to 
1001, 

- 1 1 1 1 used as filler digit, two 
digits per octet, 

- bit 4 to 1 of octet n encoding 
digit 2n-1 

- bit 8 to 5 of octet n encoding 
digit 2n 

-Number of decimal digits shall 
be from 6 to 15 starting with 
the digits from the PLIVIN 
identity. 

When the IIVISI is made of an 
odd number of digits, the filler 
digit shall be added at the end 
to make an even number of 
digits of length 2N. The filler 
digit shall then be 
consequently encoded as bit 8 
to 5 of octet N. 


>IMEI 






OCTET 
STRING 
(SIZE (8)) 


- hexadecimal digits to F, 
two hexadecimal digits per 
octet, 

- each hexadecimal digit 
encoded 0000 to 1111, 

- 1 1 1 1 used as filler for bits 8 
to 5 of last octet 

- bit 4 to 1 of octet n encoding 
digit 2n-l 

- bit 8 to 5 of octet n encoding 
digit 2n 

Number of hexadecimal digits 
shall be 15. 



9.2.1.10 



OMCID 



A variable length element indicating the destination address of the Operation and Maintenance Center (OMC) to which 
trace information is to be sent. 



IE/Group Name 


Presence 


Range 


IE type and 
reference 


Semantics description 


OMCID 


M 




OCTET 
STRING 
(3. .22) 


Coded as the OMC ID 
specified in UMTS TS based 
on GSM [25]. 



NOTE: Due to inconsistency in the definition of OMC ID between TS 25.413 and [24], it shall be ensured that the 
OMC ID IE is coded with at least the minimum number of octets required. 

9.2.1 .1 1 Integrity Protection Information 

This element contains the integrity protection information (key and permitted algorithms). 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



99 



ETSI TS 125 413 V4.10.0 (2003-09) 



IE/Group Name 


Presence 


Range 


IE type and 
reference 


Semantics description 


Integrity Protection 
Information 










>Permitted Integrity 
Protection Algorithms 










»lntegrity Protection 
Algorithm 


M 


1 to 16 


INTEGER ( 
standard UIA1 (0) 
) 


Value range is to 15. 
Only one value used. 


>lntegrity Protection Key 


M 




BIT STRING (128) 





9.2.1.12 Encryption Information 

This element contains the user data encryption information (key and permitted algorithms) used to control any 
encryption equipment at the RNC. 



IE/Group Name 


Presence 


Range 


IE type and 
reference 


Semantics description 


Encryption Information 










>Permitted Encryption 
Algorithms 










»Encryption Algorithm 


M 


1 to 16 


INTEGER (no 
encryption (0), 
standard UEA1 

(D) 


Value range is to 15. 
Only two values used. 


>Encryption Key 


M 




Bit string (128) 





9.2.1 .13 Chosen Integrity Protection Algorithm 

This element indicates the integrity protection algorithm being used by the RNC. 



IE/Group Name 


Presence 


Range 


IE type and 
reference 


Semantics description 


Chosen Integrity Protection 


M 




INTEGER ( 


Value range is to 15. 


Algorithm 






standard UIA1 (0), 
no value (15)) 


Only one value used. 
The value "no value" 
shall only be used in 
case of RANAP signalling 
over MAP/E [23]. 



9.2.1 .14 Chosen Encryption Algorithm 

This element indicates the encryption algorithm being used by the RNC. 



IE/Group Name 


Presence 


Range 


IE type and 
reference 


Semantics description 


Chosen Encryption Algorithm 


M 




INTEGER (no 
encryption (0), 
standard UEA1 

(D) 


Value range is to 15. 
Only two values used. 



9.2.1.15 

Void. 



Categorisation Parameters 



9.2.1.16 Request Type 

This element indicates the type of UE location to be reported from RNC and it is either a Service Area or Geographical 
Area. 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



100 



ETSI TS 125 413 V4.10.0 (2003-09) 



IE/Group Name 


Presence 


Range 


IE type and 
reference 


Semantics description 


Request Type 










>Event 


M 




ENUMERATED( 
Stop Change of 
service area. 
Direct, Change 
of service area, 
..., Stop Direct) 




>Report Area 


M 




ENUMERATED( 
Service Area, 
Geographical 
Area, ...) 


When the Event IE is set to 
"Stop Change of service 
area" or to "Stop Direct", 
the value of the Report 
area IE shall be the same 
as in the LOCATION 
REPORTING CONTROL 
message that initiated the 
location reporting. 


>Accuracy Code 







INTEGER( 
0..127) 


The requested accuracy "r" 
is derived from the 
"accuracy code" k by 
r= 10x(1.l''-1). 
The Accuracy Code IE 
shall be understood as the 
horizontal accuracy code. 



9.2.1.17 



Data Volume Reporting Indication 



This information element indicates whether or not RNC has to calculate the unsuccessfully transmitted NAS data 
amount for the RAB and to report the amount of data when the RAB is released. 



IE/Group Name 


Presence 


Range 


IE type and 
reference 


Semantics description 


Data Volume Reporting 
Indication 


M 




ENUMERAT 
ED (do 
report, do 
not report) 





9.2.1.18 



User Plane Mode 



This element indicates the mode of operation of the lu User plane requested for realising the RAB. The lu User plane 
modes are defined in [6]. 



IE/Group Name 


Presence 


Range 


IE type and 
reference 


Semantics description 


User Plane Mode 


M 




ENUMERAT 

ED 

(transparent 

mode, 

support 

mode for 

predefined 

SDU sizes, 

...) 


This IE contains the mode of 
operation of the lu UP protocol 



9.2.1.19 



UP Mode Versions 



UP mode versions IE is an information element that is sent by CN to RNC. It is a bit string that indicates the versions 
for the selected lu UP mode that are required and supported by the CN. The lu User plane mode versions shall be 
defined and coded as the "lu UP Mode versions supported" field defined in [6]. This reference is applicable for both the 
transparent mode and the support mode for predefined SDU sizes. 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



101 



ETSI TS 125 413 V4.10.0 (2003-09) 



IE/Group Name 


Presence 


Range 


IE type and 
reference 


Semantics description 


UP IVIode Versions 


M 




BIT STRING 
(16) 


Indicates the versions of the 
selected UP mode that are 
required and supported by the 
CN 



9.2.1.20 

Void. 



Chosen UP Version 



9.2.1.21 



Paging Area ID 



This element uniquely identifies the area, where the PAGING message shall be broadcasted. The Paging area ID is 
either a Location Area ID or Routing Area ID. 



IE/Group Name 


Presence 


Range 


IE type and 
reference 


Semantics description 


Choice Paging Area ID 










>LAI 






9.2.3.6 




>RAI 










»LAI 


M 




9.2.3.6 




»RAC 


M 




9.2.3.7 





9.2.1.22 Non Searching Indication 

This parameter allows the RNC not to search Common ID when receiving a PAGING message from the CN. 



IE/Group Name 


Presence 


Range 


IE type and 
reference 


Semantics description 


Non Searching Indication 


M 




ENUMERAT 
ED (non- 
searching, 
searching) 





9.2.1.23 Relocation Type 

This information element indicates whether the relocation of SRNS is to be executed with or without involvement of the 
UE. If the UE is involved then a radio interface handover command shall be sent to the UE to trigger the execution of 
the relocation. If the UE is not involved then the relocation execution is triggered via lur. 



IE/Group Name 


Presence 


Range 


IE type and 
reference 


Semantics description 


Relocation Type 


M 




ENUMERATED 
(UE not involved 
in relocation of 
SRNS,UE 
involved in 
relocation of 
SRNS) 





9.2.1.24 



Source ID 



Source ID IE identifies the source for the relocation of SRNS. The Source ID may be e.g. Source RNC-ID (for UMTS- 
UMTS relocation) or the SAI of the relocation source (in case of UMTS to GSM relocation). 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



102 



ETSI TS 125 413 V4.10.0 (2003-09) 



IE/Group Name 


Presence 


Range 


IE type and 
reference 


Semantics description 


Choice Source ID 










>Source RNC-ID 


- 








»PLMN identity 


M 




OCTET 
STRING 
(SIZE (3)) 


- digits to 9, encoded 0000 to 
1001, 

- 1111 used as filler digit, 
two digits per octet, 

- bits 4 to 1 of octet n encoding 
digit 2n-1 

- bits 8 to 5 of octet n encoding 
digit 2n 

-The PLIVIN identity consists of 

3 digits from IVICC followed by 

either 

-a filler digit plus 2 digits from 

MNC (in case of 2 digit IVINC) 

or 

-3 digits from I\/1NC (in case of 

a 3 digit MNC). 


»RNC-ID 


M 




INTEGER 
(0..4095) 




>SAI 


- 




9.2.3.9 





9.2.1.25 Target ID 

Target ID IE identifies the target for the relocation of SRNS. The target ID may be e.g. Target RNC-ID (for UMTS- 
UMTS relocation) or Cell Global ID of the relocation target (in case of UMTS to GSM relocation). 



IE/Group Name 


Presence 


Range 


IE type and 
reference 


Semantics description 


Choice Target ID 










>Target RNC-ID 










»LAI 


M 




9.2.3.6 




»RAC 







9.2.3.7 




»RNC-ID 


M 




INTEGER 
(0..4095) 




>CGI 










»LAI 


M 




9.2.3.6 




»CI 


M 




OCTET 
STRING (2) 





9.2.1.26 MS Classmark 2 

The coding of this element is described in [10]. 



IE/Group Name 


Presence 


Range 


IE type and 
reference 


Semantics description 


IVIS Classmark 2 


M 




OCTET 
STRING 


Contents defined in [10] 



9.2.1.27 MS Classmark 3 

The coding of this element is described in [10]. 



IE/Group Name 


Presence 


Range 


IE type and 
reference 


Semantics description 


IVIS Classmark 3 


M 




OCTET 
STRING 


Contents defined in [10] 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 103 ETSI TS 125 413 V4.10.0 (2003-09) 

9.2.1 .28 Source RNC to Target RNC Transparent Container 

Source RNC to Target RNC Transparent Container IE is an information element that is produced by source RNC and is 
transmitted to target RNC. In inter-system handover the IE is transmitted from external relocation source to target RNC. 

This IE is transparent to CN. 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



104 



ETSI TS 125 413 V4.10.0 (2003-09) 



IE/Group Name 


Presence 


Range 


IE type 

and 

reference 


Semantics 
description 


Criticallty 


Assigned 
Criticallty 


RRC Container 


M 




OCTET 
STRING 




- 


- 


Number of lu 
Instances 


M 




INTEGER 

(1-2) 




- 


- 


Relocation Type 


M 




9.2.1.23 




- 


- 


Chosen Integrity 
Protection Algorithm 







9.2.1.13 


Indicates the 
integrity protection 
algorithm. 






Integrity Protection 
Key 







Bit String 
(128) 




- 


- 


Chosen Encryption 
Algorithm 







9.2.1.14 


Indicates the 
algorithm for 
ciphering of 
signalling data. 






Ciphering Key 







Bit String 
(128) 




- 


- 


Chosen Encryption 
Algorithm 







9.2.1.14 


Indicates the 
algorithm for 
ciphering of CS user 
data. 






Chosen Encryption 
Algorithm 







9.2.1.14 


Indicates the 
algorithm for 
ciphering of PS user 
data. 






d-RNTI 


c- 

ifUEnotinvo 
Ived 




INTEGER 
(0.. 104857 
5) 








Target Cell ID 


C- 

IfUEinvolve 

d 




INTEGER 

(0..268435 

455) 


This information 
element identifies a 
cell uniquely within 
UTRAN and consists 
of RNC-ID(12bits) 
andC-ID(16bits)as 
defined in TS 25.401 
[3]. 






RAB TrCH Mapping 





1 to 

<maxnoof 

RABs> 










>RAB ID 


M 




9.2.1.2 




- 


- 


>RAB Subflow 


M 


1 to 

<maxRAB- 

Subflows> 




The RAB Subflows 
shall be presented in 
an order that 
corresponds to the 
order in which the 
RBs are presented 
per RAB in the RRC 
container included in 
this IE. 






» Transport 
Channel IDs 










- 


- 


>» DCH ID 







INTEGER 
(0..255) 


TheDCH ID is the 
identifier of an active 
dedicated transport 
channel. It is unique 
for each active DCH 
among the active 
DCHs 

simultaneously 
allocated for the 
same UE. 







£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



105 



ETSI TS 125 413 V4.10.0 (2003-09) 



>» DSCH ID 







INTEGER 
(0..255) 


TheDSCH ID is the 
identifier of an active 
downlink shared 
transport channel. It 
is unique for each 
DSCH among the 
active DSCHs 
simultaneously 
allocated for the 
same UE. 






>» USCH ID 







INTEGER 
(0..255) 


TheUSCH ID is the 
identifier of an active 
uplink shared 
transport channel. It 
is unique for each 
USCH among the 
active USCHs 
simultaneously 
allocated for the 
same UE. 






>CN Domain 
Indicator 


M 




9.2.1.5 




YES 


Ignore 


SRB TrCH 
Mapping 





1 to 

<maxnoofS 

RBs> 






GLOBAL 


Reject 


>SRB ID 


M 




INTEGER 

(1..32) 


The SRB ID is the 
absolute value of the 
SRB. 






>DCH ID 







INTEGER 
(0..255) 


TheDCH ID is the 
identifier of an active 
dedicated transport 
channel over lur. It is 
unique for each 
active DCH among 
the active DCHs 
simultaneously 
allocated for the 
same UE. 






>DSCH ID 







INTEGER 
(0..255) 


TheDSCH ID is the 
identifier of an active 
downlink shared 
transport channel 
over lur. It is unique 
for each DSCH 
among the active 
DSCHs 

simultaneously 
allocated for the 
same UE. 






>USCH ID 







INTEGER 
(0..255) 


TheUSCH ID is the 
identifier of an active 
uplink shared 
transport channel 
over lur. It is unique 
for each USCH 
among the active 
USCHs 

simultaneously 
allocated for the 
same UE. 







£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



106 



ETSI TS 125 413 V4.10.0 (2003-09) 



Condition 


Explanation 


IfUEnotinvolved 


This IE shall be present if the Relocation type IE is set to "UE not 
involved in relocation of SRNS". 


IfUEInvoived 


This IE shall be present if the Relocation type IE is set to "UE 
involved in relocation of SRNS". 



Range bound 


Explanation 


maxnoofRABs 


Maximum no. of RABs for one UE. Value is 256. 


maxRABSubflows 


IVIaximum no. of subflows per RAB. Value is 7. 


maxnoofSRBs 


Maximum no. of SRBs per RAB. Value is 8. 



9.2.1 .29 Old BSS to New BSS Information 

The coding of this element is described in [11]. 



IE/Group Name 


Presence 


Range 


IE type and 
reference 


Semantics description 


Old BSS To New BSS 


M 




OCTET 


Coded as the Old BSS to New 


Information 






STRING 


BSS information elements field 
of the Old BSS to New BSS 
Information IE defined in [11]. 



9.2.1 .30 Target RNC to Source RNC Transparent Container 

Target RNC to Source RNC Transparent Container IE is an information element that is produced by target RNC and is 
transmitted to source RNC. In inter-system handover the IE is transmitted from target RNC to the external relocation 
source. 

This IE is transparent to CN. 



IE/Group Name 


Presence 


Range 


IE type and 
reference 


Semantics description 


RRC Container 


M 




OCTET 
STRING 




d-RNTI 







INTEGER 
(0.. 1048575) 


May be included to allow the 
triggering of the Relocation 
Detect procedure from the lur 
Interface 



9.2.1.31 L3 Information 

The coding of this element is described in [11]. 



IE/Group Name 


Presence 


Range 


IE type and 
reference 


Semantics description 


L3 Information 


M 




OCTET 
STRING 


Coded as the value part of the 
Layer 3 Information IE defined 
in [11] (i.e. excluding the 
Element Identifier and the 
/.engff/? fields). 



9.2.1.32 Number of Steps 

Indicates the number of steps to reduce traffic in overload situation. 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



107 



ETSI TS 125 413 V4.10.0 (2003-09) 



IE/Group Name 


Presence 


Range 


IE type and 
reference 


Semantics description 


Number Of Steps 


M 




INTEGER 

(1..16) 





9.2.1 .33 DL N-PDU Sequence Number 

This IE indicates the radio interface sequence number (PDCP) [17] of the next downHnk N-PDU (PDCP SDU) that 
would have been sent to the UE by a source system. 



IE/Group Name 


Presence 


Range 


IE type and 
reference 


Semantics description 


DL N-PDU Sequence 
Number 


M 




INTEGER (0 
..65535) 


This IE indicates the sequence 
number of the next DL N-PDU 
that would have been sent to 
the UE by a source system. 
This is the 16 bit sequence 
number. 



9.2.1 .34 UL N-PDU Sequence Number 

This IE indicates the radio interface sequence number (PDCP) [17] of the next uplink N-PDU (PDCP SDU) that would 
have been expected from the UE by a source system. 



IE/Group Name 


Presence 


Range 


IE type and 
reference 


Semantics description 


UL N-PDU Sequence 
Number 


M 




INTEGER (0 
..65535) 


This IE indicates the sequence 

number of the next UL N-PDU 

that would have been 

expected from the UE by a 

source system. 

This is the 16 bit sequence 

number. 



9.2.1 .35 Criticality Diagnostics 

The Criticality Diagnostics IE is sent by the RNC or the CN when parts of a received message have not been 
comprehended or were missing, or if the message contained logical errors. When applicable, it contains information 
about which lEs that were not comprehended or were missing. 

For further details on how to use the Criticality Diagnostics IE, see Annex A.2. 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



108 



ETSI TS 125 413 V4.10.0 (2003-09) 



IE/Group Name 


Presence 


Range 


IE type and 
reference 


Semantics description 


Criticality Diagnostics 










>Procedure Code 







INTEGER 
(0..255) 


Procedure Code is to be used 
if Criticality Diagnostics is part 
of Error Indication procedure, 
and not within the response 
message of the same 
procedure that caused the 
error 


>Triggering Message 







ENUMERAT 

ED(initiating 

message, 

successful 

outcome, 

unsuccessful 

outcome, 

outcome) 


The Triggering Message is 
used only if the Criticality 
Diagnostics is part of Error 
Indication procedure. 


>Procedure Criticality 







ENUMERAT 
ED(reject, 
ignore, 
notify) 


This Procedure Criticality is 
used for reporting the 
Criticality of the Triggering 
message (Procedure). 


Information Element 
Criticality Diagnostics 




to <maxnoof 
errors> 






>IE Criticality 


M 




ENUMERAT 
ED(reject, 
ignore, 
notify) 


The IE Criticality is used for 
reporting the criticality of the 
triggering IE. The value 
'ignore' shall not be used. 


>IEID 


M 




INTEGER 
(0. .65535) 


The IE ID of the not 
understood or missing IE 


>Repetition Number 







INTEGER 
(0..255) 


The Repetition Number \E 
gives 

• in case of a not 
understood IE: 
The number of 
occurrences of the 
reported IE up to and 
including the not 
understood occurrence 

• in case of a missing IE: 
The number of 
occurrences up to but not 
including the missing 
occurrence. 

Note: All the counted 
occurrences of the reported IE 
must have the same topdown 
hierachical message structure 
of lEs with assigned criticality 
above them. 


>Message Structure 







9.2.1.42 


The Message Structure IE 
describes the structure where 
the not understood or missing 
IE was detected. 
This IE is included if the not 
understood IE is not the top 
level of the message. 


>Type of Error 


M 




ENUMERAT 
ED(not 
understood, 
missing, ...) 





£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



109 



ETSI TS 125 413 V4.10.0 (2003-09) 



Range bound 


Explanation 


maxnooferrors 


Maximum no. of IE errors allowed to be reported with a single 
message. The value for maxnooferrors is 256. 



9.2.1.36 Key Status 

This IE tells if the keys included in SECURITY MODE COMMAND message are new or if they have been used 
previously. 



IE/Group Name 


Presence 


Range 


IE type and 
reference 


Semantics description 


Key Status 


M 




ENUMERAT 
ED (old, 
new, ...) 





9.2.1 .37 DRX Cycle Length Coefficient 

This IE indicates the DRX cycle length coefficient (k) as defined in [10]. 



IE/Group Name 


Presence 


Range 


IE type and 
reference 


Semantics description 


DRX Cycle Length Coefficient 


M 




INTEGER 
(6..9) 





9.2.1.38 lu Signalling Connection Identifier 



IE/Group Name 


Presence 


Range 


IE type and 
reference 


Semantics description 


lu Signalling Connection 
Identifier 


M 




BIT STRING 
(SIZE(24)) 


The most significant bit of this 

IE shall indicate the node, that 

has assigned the value. 

MSB = "0": assigned by the 

RNC 

MSB = "1 ": assigned by the 

CN 



9.2.1.39 Global RNC-ID 

Global RNC-ID is used to globally identify an RNC. 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



110 



ETSI TS 125 413 V4.10.0 (2003-09) 



IE/Group Name 


Presence 


Range 


IE type and 
reference 


Semantics description 


Global RNC-ID 










>PLMN identity 


M 




OCTET 
STRING 
(SIZE (3)) 


- digits to 9, encoded 0000 to 
1001, 

- 1111 used as filler digit, 
two digits per octet, 

- bits 4 to 1 of octet n encoding 
digit 2n-1 

- bits 8 to 5 of octet n encoding 
digit 2n 

-The PLIVIN identity consists of 

3 digits from IVICC followed by 

either 

-a filler digit plus 2 digits from 

IVINC (in case of 2 digit MNC) 

or 

-3 digits from MNC (in case of 

a 3 digit MNC). 


>RNC-ID 


M 




INTEGER 
(0..4095) 





9.2.1 .40 PDP Type Information 



IE/Group Name 


Presence 


Range 


IE type and 
reference 


Semantics description 


PDP Type Information 










>PDP Type 


M 


1 to 

<maxnoofPDPDir 
ections> 


ENUMERAT 

ED(empty, 

PPP, 

OSP:IHOSS, 

IPv4, 

IPv6,...) 


PDP Type is defined in [8], 

and the restrictions on usage 

shall comply with [8]. 

Usage: 

When the IE is repeated then 

PDP Type for downlink is 

signalled first, followed by PDP 

Type for uplink; when the IE is 

not repeated, the PDP Type 

shall apply to both uplink and 

downlink. 

OSP:IHOSS: This value shall 

not be used. 



Range bound 


Explanation 


maxnoofPDPDirections 


Number of directions for which PDP Type is signalled separately 



9.2.1.41 Service Handover 

This IE tells if intersystem handover to GSM should, should not, or shall not be performed for the RAB in question. 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



111 



ETSI TS 125 413 V4.10.0 (2003-09) 



IE/Group Name 


Presence 


Range 


IE type and 
reference 


Semantics description 


Service Handover 


M 




ENUMERAT 
ED 

(Handover to 
GSM should 
be 

performed. 
Handover to 
GSM should 
not be 
performed. 
Handover to 
GSM shall 
not be 
performed. 





9.2.1 .42 Message Structure 

The Message Structure IE gives information for each level with assigned criticality in an hierachical message structure 
from top level down to the lowest level above the reported level for the occured error (reported in the Information 
Element Criticality Diagnostics IE). 



IE/Group Name 


Presence 


Range 


IE type 

and 

reference 


Semantics 
description 


Criticality 


Assigned 
Criticality 


Message 
structure 




1 to 

<maxnoofle 

vels> 




The first repetition of 
the Message 
Structure IE 
corresponds to the 
top level of the 
message. The last 
repetition of the 
Message Structure 
IE corresponds to 
the level above the 
reported level for the 
occured error of the 
message. 


GLOBAL 


ignore 


>IEID 


M 




INTEGER 
(0..65535) 


The IE ID of this 
level's IE containing 
the not understood 
or missing IE. 






>Repetition 
Number 







INTEGER 
(1..256) 


The Repetition 
Number \E gives, if 
applicable, the 
number of 
occurrences of this 
level's reported IE 
up to and including 
the occurrence 
containing the not 
understood or 
missing IE. 

Note: All the counted 
occurrences of the 
reported IE must 
have the same 
topdown hierachical 
message structure 
of lEs with assigned 
criticality above 
them. 







£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



112 



ETSI TS 125 413 V4.10.0 (2003-09) 



Range bound 


Explanation 


maxnooflevels 


Maximum no. of message levels to report. The value for 
maxnooflevels is 256. 



9.2.1.43 



Alternative RAB Parameter Values 



The purpose of the Alternative RAB Parameter Values IE is to indicate that RAB QoS negotiation is allowed for certain 
RAB parameters and in some cases also which alternative values to be used in the negotiation. 



IE/Group Name 


Presence 


Range 


IE type and 
reference 


Semantics description 


Alternative RAB parameter 
values 










>Alternative Maximum 
Bit Rate Information 









Included only if negotiation is 
allowed for this IE. 


»Type of Alternative 
Maximum Bit Rate 
Information 


M 




ENUMERATED 
(Unspecified, 
Value range, 
Discrete values) 


Unspecified means that 
negotiation is allowed, but no 
alternative values are provided 
from the CN i.e. the RNC is 
allowed to assign any value 
equal or below the ones 
indicated in the RAB Parameters 
IE. 


»Alternative 
Maximum Bit Rates 


0- 

ifValueRan 
georDiscre 
teValuesM 
BR 


1 to <nbr- 

Alternative 

Values> 




For Value Range, one value limit 
is given here and the other given 
by Maximum Bit Rate in the RAB 
Parameters IE. 
For Discrete Values, 1 to 16 
discrete values can be given. 


»>Bit Rate 


M 


1 to <nbr- 

SeparateTrafficDIr 

ections> 


INTEGER 
(1.. 16,000,000) 


When nbr- 

SeparateTrafficDirections is 
equal to 2, then the Bit Rate 
attribute for downlink is signalled 
first, then the Bit Rate atthbute 
for uplink. 


>Alternative Guaranteed 
Bit Rate Information 









Included only if negotiation is 
allowed for this IE. 


»Type of Alternative 
Guaranteed Bit Rate 
Information 


M 




ENUMERATED 
(Unspecified, 
Value range, 
Discrete values) 


Unspecified means that 
negotiation is allowed, but no 
alternative values are provided 
from the CN i.e. the RNC is 
allowed to assign any value 
equal or below the ones 
indicated in the RAB Parameters 
IE. 


»Alternative 
Guaranteed Bit Rates 


C 

IfValueRan 
georDiscre 
teValuesG 
BR 


1 to <nbr- 

Alternative 

Values> 




For Value Range, one value limit 
is given here and the other given 
by Guaranteed Bit Rate in the 
RAB Parameters IE. 
For Discrete Values, 1 to 16 
discrete values can be given. 


»>Bit Rate 


M 


1 to <nbr- 

SeparateTrafficDIr 

ections> 


INTEGER 
(0.. 16,000,000) 


When nbr- 

SeparateTrafficDirections is 
equal to 2, then the Bit Rate 
attribute for downlink is 
signalled first, then the Bit Rate 
attribute for uplink. 



Range Bound 


Explanation 


nbr-Alternative Values 


Maximum number of alternative values. 
Value is 1 in case of Value Range and 
16 in case of Discrete Values. 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



113 



ETSI TS 125 413 V4.10.0 (2003-09) 



nbr-SeparateTrafficDirection 


Number of Traffic Directions being signalled 
separately. 

Set to 2 if RAB asymmetry indicator is 
asymmetric bidirectional. 

Set to 1 in all other cases. 



Condition 


Explanation 


ifValueRangeorDiscreteValuesMBR 


This IE shall be present if the Type of Alternative Maximum Bit 
Rates Information IE is set to "Value range" or "Discrete values". 


ifValueRangeorDiscreteValuesGBR 


This IE shall be present if the Type of Guaranteed Bit Rates 
Information IE is set to "Value range" or "Discrete values". 



9.2.1 .44 Assigned RAB Parameter Values 

The purpose of the Assigned RAB Parameter Values IE is to indicate that RAB QoS negotiation has been performed for 
certain RAB parameters and which values that have been chosen. 



IE/Group Name 


Presence 


Range 


IE type and 
reference 


Semantics description 


Assigned RAB parameter 
values 










>Assigned Maximum Bit 
Rate 





1 to <nbr- 

SeparateTrafficDIr 

ections> 


INTEGER 
(1.. 16,000,000) 


When nbr- 

SeparateTrafficDirections is 
equal to 2, then Assigned 
Maximum Bit Rate attribute for 
downlink is signalled first, then 
Assigned Maximum Bit Rate 
attribute for uplink. 


>Assigned Guaranteed 
Bit Rate 





1 to <nbr- 

SeparateTrafficDir 

ections> 


INTEGER 
(0.. 16,000,000) 


When nbr- 

SeparateTrafficDirections is 
equal to 2, then Assigned 
Guaranteed Bit Rate for 
downlink is signalled first, then 
Assigned Guaranteed Bit Rate 
for uplink. 



Range Bound 


Explanation 


nbr-SeparateTrafficDirection 


Number of Traffic Directions being signalled 

separately. 

Set to 2 if RAB asymmetry indicator is 

asymmetric bidirectional. 

Set to 1 in all other cases. 



9.2.1 .45 Requested RAB Parameter Values 

The purpose of Requested RAB Parameter Values IE is to indicate the RAB parameters for which different values are 
being requested, as well as those different RAB parameter values. 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



114 



ETSI TS 125 413 V4.10.0 (2003-09) 



IE/Group Name 


Presence 


Range 


IE type and 
reference 


Semantics description 


Requested RAB Parameter 
Values 










>Requested Maximum 
Bit Rate 





to <nbr- 

SeparateTraffic 

Directions> 


INTEGER 
(1.. 16,000,000) 


When nbr- 

SeparateTrafficDirections is 
equal to 2, Requested Maximum 
Bit Rate attribute for downlink is 
signalled first, then Requested 
Maximum Bit Rate attribute for 
uplink. 


>Requested Guaranteed 
Bit Rate 





to <nbr- 

SeparateTraffic 

Directions> 


INTEGER 
(0.. 16,000,000) 


When nbr- 

SeparateTrafficDirections is 
equal to 2, Requested 
Guaranteed Bit Rate for 
downlink is signalled first, then 
Requested Guaranteed Bit Rate 
for uplink. 



Range bound 


Explanation 


nbr-SeparateTrafficDirection 


Number of Traffic Directions being signalled 

separately. 

Set to 2 if RAB Asymmetry Indicator is 

asymmetric bidirectional. 

Set to 1 in all other cases. 



9.2.1.46 Global CN-ID 

Global CN-ID is used to globally identify a CN node. 



IE/Group Name 


Presence 


Range 


IE type and 
reference 


Semantics description 


Global CN-ID 










>PLMN identity 


M 




OCTET 
STRING 
(SIZE (3)) 


- digits to 9, encoded 0000 to 
1001, 

- 1111 used as filler digit, 
two digits per octet, 

- bits 4 to 1 of octet n encoding 
digit 2n-1 

- bits 8 to 5 of octet n encoding 
digit 2n 

-The PLMN identity consists of 

3 digits from MOO followed by 

either 

-a filler digit plus 2 digits from 

MNC (in case of 2 digit MNG) 

or 

-3 digits from MNG (in case of 

a 3 digit MNG). 


>CN-ID 


M 




INTEGER 
(0..4095) 





9.2.1 .46a Vertical Accuracy Code 

This element includes information about the requested vertical accuracy. 



IE/Group Name 


Presence 


Range 


IE type and 
reference 


Semantics description 


Vertical Accuracy Code 










>Vertical Accuracy Gode 


M 




INTEGER( 
0..127) 


The requested accuracy 
"v" is derived from the 
"accuracy code" k by 
v = 45x(1.025''-1). 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



115 



ETSI TS 125 413 V4.10.0 (2003-09) 



9.2.1.46b Response Time 

This element includes information about the requested response time. 



IE/Group Name 


Presence 


Range 


IE type and 
reference 


Semantics description 


Response Time 










>Response Time 


M 




ENUMERATED 
(Low Delay, 
Delay Tolerant, 


The value refers to [26]. 



9.2.1.46c Positioning Priority 

This element includes information about the requested positioning priority. 



IE/Group Name 


Presence 


Range 


IE type and 
reference 


Semantics description 


Positioning Priority 










>Positioning Priority 


M 




ENUMERATED! 
High Priority, 
Normal Priority, 


The value refers to [26]. 



9.2.1. 46d Client Type 

This element includes information about the client type. 



IE/Group Name 


Presence 


Range 


IE type and 
reference 


Semantics description 


Client Type 










>Client Type 


M 




ENUMERATED! 
Emergency 
Services, Value 
Added Services, 
PLMN Operator 
Services, Lawful 
Intercept 
Services, PLMN 
Operator - 
broadcast 
services, PLMN 
Operator - O&M, 
PLMN Operator 
- anonymous 
statistics, PLMN 
Operator - 
Target MS 
service support, 


Identifies the type of client. 



9.2.2 Transport Network Layer Related lEs 



9.2.2.1 



Transport Layer Address 



For the PS domain this information element is an IP address to be used for the user plane transport. For the CS domain 
this address is to be used for Transport Network Control Plane signalling to set up the transport bearer. 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



116 



ETSI TS 125 413 V4.10.0 (2003-09) 



IE/Group Name 


Presence 


Range 


IE type and 
reference 


Semantics description 


Transport Layer Address 


M 




BIT STRING 

(1..160, ...) 


The Radio Network layer is not 
supposed to interpret the 
address information. It should 
pass it to the transport layer 
for interpretation. 
For details on the Transport 
Layer Address, see ret. [9]. 



9.2.2.2 



lu Transport Association 



This element is used to associate the RAB and the corresponding transport bearer. For the CS domain this information 
element is the Binding ID to be used in Transport Network Control Plane signalling during set up of the transport 
bearer. In PS domain this information element is the GTP Tunnel Endpoint Identifier. 



IE/Group Name 


Presence 


Range 


IE type and 
reference 


Semantics description 


Choice lu Transport 
Association 










>GTP TEID 






OCTET 
STRING (4) 




>Binding ID 






OCTET 
STRING (4) 





9.2.2.3 DL GTP-PDU Sequence Number 

This IE indicates the sequence number of the GTP-PDU which is the next to be sent to the UE. 



IE/Group Name 


Presence 


Range 


IE type and 
reference 


Semantics description 


DL GTP-PDU Sequence 


M 




INTEGER (0 


This IE indicates the sequence 


Number 






..65535) 


number of the GTP-PDU 
which is next to be sent to the 
UE. 



9.2.2.4 UL GTP-PDU Sequence Number 

This IE indicates the sequence number of the GTP-PDU which is the next to be sent to the SGSN. 



IE/Group Name 


Presence 


Range 


IE type and 
reference 


Semantics description 


UL GTP-PDU Sequence 


M 




INTEGER (0 


This IE indicates the sequence 


Number 






..65535) 


number of the GTP-PDU 
which is next to be sent to the 
SGSN. 



9.2.3 NAS Related lEs 



9.2.3.1 



Permanent NAS UE Identity 



This element is used to identify the UE commonly in UTRAN and in CN. RNC uses it to find other existing signalling 
connections of this same UE (e.g. RRC or lu signalling connections) Initially this is of the type of IMSI. 

NOTE: IMSI is specified in the [19]. 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



117 



ETSI TS 125 413 V4.10.0 (2003-09) 



IE/Group Name 


Presence 


Range 


IE type and 
reference 


Semantics description 


Choice Permanent NAS UE 
Identity 










>IMSI 


M 




OCTET 
STRING 
(SIZE (3..8)) 


- digits to 9, encoded 0000 to 
1001, 

- 1111 used as filler digit, 
two digits per octet, 

- bit 4 to 1 of octet n encoding 
digit 2n-1 

- bit 8 to 5 of octet n encoding 
digit 2n 

-Number of decimal digits shall 
be from 6 to 15 starting with 
the digits from the PLIVIN 
identity. 

When the IIVISI is made of an 
odd number of digits, the filler 
digit shall be added at the end 
to make an even number of 
digits of length 2N. The filler 
digit shall then be 
consequently encoded as bit 8 
to 5 of octet N. 



9.2.3.2 Temporary UE ID 

Temporary Mobile Subscriber Identity, used for security reasons to hide the identity of a subscriber. 



IE/Group Name 


Presence 


Range 


IE type and 
reference 


Semantics description 


Choice Temporary UE ID 










>TMSI 






OCTET 
STRING (4) 




>P-TMS1 






OCTET 
STRING (4) 





9.2.3.3 Paging Cause 

This element indicates the cause of paging to the UE. 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



118 



ETSI TS 125 413 V4.10.0 (2003-09) 



IE/Group Name 


Presence 


Range 


IE type and 
reference 


Semantics description 


Paging Cause 


M 




ENUMERAT 

ED( 

Terminating 

Conversatio 

nal Call, 

Terminating 

Streaming 

Call, 

Terminating 

Interactive 

Call, 

Terminating 

Background 

Call, 

Terminating 

Low Priority 

Signalling, 

Terminating 
High Priority 
Signalling) 





9.2.3.4 

Void 

9.2.3.5 



NAS Broadcast Information 



NAS PDU 



This information element contains the CN - UE or UE - CN message that is transferred without interpretation in the 
RNC. Typically it contains call control, session management, supplementary services, short message service and 
mobility management messages. 



IE/Group Name 


Presence 


Range 


IE type and 
reference 


Semantics description 


NAS PDU 


M 




OCTET 
STRING 





9.2.3.6 LAI 

This element is used to uniquely identify a Location Area. 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



119 



ETSI TS 125 413 V4.10.0 (2003-09) 



IE/Group Name 


Presence 


Range 


IE type and 
reference 


Semantics description 


LAI 










>PLMN identity 


M 




OCTET 
STRING 
(SIZE (3)) 


- digits to 9, encoded 0000 to 
1001, 

- 1111 used as filler digit, 
two digits per octet, 

- bits 4 to 1 of octet n encoding 
digit 2n-1 

- bits 8 to 5 of octet n encoding 
digit 2n 

-The PLIVIN identity consists of 

3 digits from IVICC followed by 

either 

-a filler digit plus 2 digits from 

IVINC (in case of 2 digit MNC) 

or 

-3 digits from MNC (in case of 

a 3 digit MNC). 


>LAC 


M 




OCTET 
STRING (2) 


0000 and FFFE not allowed. 



9.2.3.7 RAG 

This element is used to identify a Routing Area within a Location Area. It is used for PS services. 



IE/Group Name 


Presence 


Range 


IE type and 
reference 


Semantics description 


RAC 


M 




OCTET 
STRING (1) 





9.2.3.8 SAPI 

The &4P/IE is used to indicate the specific service provided for the message. 



IE/Group Name 


Presence 


Range 


IE type and 
reference 


Semantics description 


SAPI 


M 




ENUMERATED 
(SAPI 0, SAPI 3, 





9.2.3.9 



SAI 



Service Area Identifier (SAI) IE information (see ref. [3]) is used to identify an area consisting of one or more cells 
belonging to the same Location Area. Such an area is called a Service Area and can be used for indicating the location 
of a UE to the CN. For this protocol, only a Service Area that is defined to be applicable to the PS and CS domains shall 
be used. 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



120 



ETSI TS 125 413 V4.10.0 (2003-09) 



IE/Group Name 


Presence 


Range 


IE type and 
reference 


Semantics description 


SAI 










>PLMN identity 


M 




OCTET 
STRING 
(SIZE (3)) 


- digits to 9, encoded 0000 to 
1001, 

- 1111 used as filler digit, 
two digits per octet, 

- bits 4 to 1 of octet n encoding 
digit 2n-1 

- bits 8 to 5 of octet n encoding 
digit 2n 

-The PLIVIN identity consists of 

3 digits from IVICC followed by 

either 

-a filler digit plus 2 digits from 

IVINC (in case of 2 digit MNC) 

or 

-3 digits from MNC (in case of 

a 3 digit MNC). 


>LAC 


M 




OCTET 
STRING (2) 


0000 and FFFE not allowed. 


>SAC 


M 




OCTET 
STRING (2) 





9.2.3.10 Area Identity 

This information element is used for indicating the location of a UE and is either a Service Area or Geographical Area. 



IE/Group Name 


Presence 


Range 


IE type and 
reference 


Semantics description 


Choice Area Identity 










>SAI 






9.2.3.9 




>Geographical Area 






9.2.3.11 





9.2.3.1 1 Geographical Area 

Geographical Area IE is used to identify an area, as seen from the CN, using geographical coordinates. The reference 
system is the same as the one used in [20]. 



IE/Group Name 


Presence 


Range 


IE type and 
reference 


Semantics description 


Choice Geographical Area 










>Point 






See below 


Ellipsoid point 


>Polnt With 
Uncertainty 






See below 


Ellipsoid point with 
uncertainty circle 


>Polygon 






See below 


List of Ellipsoid points 


>Elllpsoid point with 
uncertainty Ellipse 






See below 


Ellipsoid point with 
uncertainty Ellipse 


>Elllpsoid point with 
altitude 






See below 


Ellipsoid point with 
altitude 


>Elllpsoid point with 
altitude and uncertainty 
Ellipsoid 






See below 


Ellipsoid point with 
altitude and uncertainty 
Ellipsoid 


>Elllpsoid Arc 






See below 


Ellipsoid Arc 




IE/Group Name 


Presence 


Range 


IE type and 
reference 


Semantics description 


Point 










>Geographical 
Coordinates 


M 




See below 





£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



121 



ETSI TS 125 413 V4.10.0 (2003-09) 



IE/Group Name 


Presence 


Range 


IE type and 
reference 


Semantics description 


Point With Uncertainty 










>Geographical 
Coordinates 


M 




See below 




>Uncertainty Code 


M 




INTEGER( 
0..127) 


The uncertainty "r" is 
derived from the 
"uncertainty code" k by 
r=10x(1.1-1) 




IE/Group Name 


Presence 


Range 


IE type and 
reference 


Semantics description 


Polygon 










>Geographical 
Coordinates 


M 


1 to 
<maxnoofPoints> 


See below 






Range bound 


Explanation 


maxnoofPoints 


IVIaximum no. of points in polygon. Value 


s15. 




IE/Group Name 


Presence 


Range 


IE type and 
reference 


Semantics description 


Ellipsoid point with 
uncertainty Ellipse 










>Geographical 
Coordinates 


M 




See below 




>Uncertainty Ellipse 


M 




See below 




>Confidence 


M 




INTEGER( 
0..127) 






IE/Group Name 


Presence 


Range 


IE type and 
reference 


Semantics description 


Ellipsoid point with 
altitude 










>Geographical 
Coordinates 


M 




See below 




>Altitude and direction 


M 




See below 






IE/Group Name 


Presence 


Range 


IE type and 
reference 


Semantics description 


Ellipsoid point with 
altitude and uncertainty 
Ellipsoid 










>Geographical 
Coordinates 


M 




See below 




>Altitude and direction 


M 




See below 




>Uncertainty Ellipse 


M 




See below 




>Uncertainty Altitude 


M 




INTEGER{ 
0..127) 




>Confidence 


M 




INTEGER( 
0..127) 





£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



122 



ETSI TS 125 413 V4.10.0 (2003-09) 



IE/Group Name 


Presence 


Range 


IE type and 
reference 


Semantics description 


Ellipsoid Arc 










>Geographical 
Coordinates 


M 




See below 




>lnner radius 


M 




INTEGER ( 


The relation between the 
value (N) and the radius 
(r) in meters it describes 
is 5N<r<5(N+1), except 
forN=2^^-1 for which the 
range is extended to 
include all grater values 
of (r). 


>Uncertainty radius 


M 




INTEGER{ 
0..127) 


The uncertainty "r" is 
derived from the 
"uncertainty code" k by 
r=10x(1.1 -1) 


>Offset angle 


M 




INTEGER( 
0..179) 


The relation between the 
value (N) and the angle 
(a) in degrees it 
describes is 
2N<a<2(N+1) 


>lncluded angle 


M 




INTEGER( 
0..179) 


The relation between the 
value (N) and the angle 
(a) in degrees it 
describes is 
2N<a<2(N+1) 


>Gonfidence 


M 




INTEGER( 
0..127) 





IE/Group Name 


Presence 


Range 


IE type and 
reference 


Semantics description 


Geographical Coordinates 










>Latitude Sign 


M 




ENUMERATED 
(North, South) 




>Degrees Of Latitude 


M 




INTEGER ( 
0..2^^-1) 


The IE value (N) is 
derived by this formula: 
N<2^^X/90<N+1 
X being the latitude in 
degree (0°.. 90°) 


>Degrees Of Longitude 


M 




INTEGER ( 
-2^1.2^^-1) 


The IE value (N) is 
derived by this formula: 
N<2^''X/360<N+1 
X being the longitude in 
degree (-180°.. +180°) 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



123 



ETSI TS 125 413 V4.10.0 (2003-09) 



IE/Group Name 


Presence 


Range 


IE type and 
reference 


Semantics description 


Uncertainty Ellipse 










>Uncertainty semi-major 


M 




INTEGER{ 
0..127) 


The uncertainty "r" is 
derived from the 
"uncertainty code" k by 
r=10x(1.r-1) 


>Uncertainty semi-minor 


M 




INTEGER( 
0..127) 


The uncertainty "r" is 
derived from the 
"uncertainty code" k by 
r=10x(1.1-1) 


>Orientation of major 
axis 


M 




INTEGER( 
0..179) 


The relation between the 
IE value (N) and the 
angle (a) in degrees it 
describes is 
2N<a<2(N+1). The 
values 90. .179 shall not 
be used. 



IE/Group Name 


Presence 


Range 


IE type and 
reference 


Semantics description 


Altitude and direction 










>Direction of Altitude 


M 




ENUMERATED 
(Height, Depth) 




>Altitude 


M 




INTEGER ( 
0..2'^-1) 


The relation between the 
value (N) and the altitude 
(a) in meters it describes 
is N<a<N-Hl, except for 
N=2^^-1 for which the 
range is extended to 
include all grater values 
of (a). 



9.2.3.1 2 Unsuccessfully Transmitted Data Volume 

This information element indicates the data volume (octets) that is unsuccessfully transmitted over the radio interface 
in DL direction for the RAB. 



IE/Group Name 


Presence 


Range 


IE type and 
reference 


Semantics description 


Unsuccessfully Transmitted 
Data Volume 


M 




INTEGER 

(0..2^^-1) 


Unit is octet. 



9.2.3.13 Data Volume Reference 

This information element indicates the time when the data volume is counted. 



IE/Group Name 


Presence 


Range 


IE type and 
reference 


Semantics description 


Data Volume Reference 


M 




INTEGER 
(0..255) 





9.2.3.14 Information Identity 

Void 

9.2.3.15 Information Priority 

Void 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



124 



ETSI TS 125 413 V4.10.0 (2003-09) 



9.2.3.16 

Void 

9.2.3.17 
Void 



Information Control 



CN Broadcast Area 



9.2.3.18 NAS Synchronisation Indicator 

This information element contains transparent NAS information that is transferred without interpretation in the RNC. 



IE/Group Name 


Presence 


Range 


IE type and 
reference 


Semantics description 


NAS Synchronisation 
Indicator 


M 




BIT STRING 

(4) 





9.2.3.19 Location Related Data Request Type 

This element indicates the type of the requested location related data for the indicated positioning method, and provides 
the assistance data for the Assisted GPS positioning method. 



IE/Group Name 


Presence 


Range 


IE type and 
reference 


Semantics description 


Location Related Data 
Request Type 










>Requested Location 
Related Data Type 


M 




ENUMERATED( 
Deciphering 
Keys for UE 
Based OTDOA, 

Deciphering 
Keys for 
Assisted GPS, 

Dedicated 
Assistance Data 
for UE Based 
OTDOA, 

Dedicated 
Assistance Data 
for Assisted 
GP"S, ...) 




>Requested GPS 
Assistance Data 


C- 

ifDedAssG 
PS 




9.2.3.21 





Condition 


Explanation 


IfDedAssGPS 


This IE shall be present if the Requested Location Related Data 
Type IE is set to 'Dedicated Assistance Data for Assisted GPS'. 



9.2.3.20 Broadcast Assistance Data Deciphering keys 

This information element is used for indicating the deciphering keys that will be used by the UE for deciphering of 
assistance data broadcast. 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



125 



ETSI TS 125 413 V4.10.0 (2003-09) 



IE/Group Name 


Presence 


Range 


IE type and 
reference 


Semantics description 


Broadcast Assistance Data 
Deciphering keys 










> Ciphering Key Flag 


M 




BIT STRING 
(SIZE(1)) 


Indicates the current Ciphering 
Key Flag that is used for the 
assistance data broadcast 
messages in the location area. 


>Current Deciphering 
key 


M 




BIT STRING 
(SIZE(56)) 


Current deciphering key that is 
used for deciphering 
assistance data. 


>Next Deciphering key 


M 




BIT STRING 
(SIZE(56)) 


Next deciphering key that will 
be used for deciphering 
assistance data. 



9.2.3.21 Requested GPS Assistance Data 

This information element is used for indicating the requested GPS assistance data. 
This IE is transparent to CN. 



IE/Group Name 


Presence 


Range 


IE type and 
reference 


Semantics description 


Requested GPS Assistance 
Data 






OCTET 

STRING 

(SIZE(1..38)) 


For the corresponding 
Information Element Definition 
see "gpsAssistanceData" [22]. 



9.2.3.22 



Last Known Service Area 



This information element is used for indicating the last known Service Area and the elapsed time since the UE was 
known to be in this Service Area. The last known Service Area is reported when the current Service Area is unknown to 
the RNC. 



IE/Group Name 


Presence 


Range 


IE type and 
reference 


Semantics description 


Last Known Service Area 










>SAI 


M 




9.2.3.9 




>Age of SAI 


M 




INTEGER 
(0..32767) 


The value represents the 
elapsed time in minutes since 
the reported last known SAI 
was stored by the RNC. 
Value "0" shall not be used. 
Value "32767" indicates that 
the age of SAI is at least 
32767 minutes old. 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 126 ETSI TS 125 413 V4.10.0 (2003-09) 

9.3 Message and Information Element Abstract Syntax (with ASN.1) 

9.3.0 General 

RANAP ASN.l definition conforms with [14] and [15]. 

The ASN.l definition specifies the structure and content of RANAP messages. RANAP messages can contain any lEs specified in the object set definitions for that message 
without the order or number of occurrence being restricted by ASN. 1 . However, for this version of the standard, a sending entity shall construct a RANAP message according to 
the PDU definitions module and with the following additional rules (Note that in the following IE means an IE in the object set with an explicit id. If one IE needed to appear 
more than once in one object set, then the different occurrences have different IE ids): 

• lEs shall be ordered (in an IE container) in the order they appear in object set definitions.. 

• Object set definitions specify how many times lEs may appear. An IE shall appear exactly once if the presence field in an object has value "mandatory". An IE may appear 
at most once if the presence field in an object has value "optional" or "conditional". If in a tabular format there is multiplicity specified for an IE (i.e. an IE list) then in the 
corresponding ASN.l definition the list definition is separated into two parts. The first part defines an IE container list where the list elements reside. The second part 
defines list elements. The IE container list appears as an IE of its own. For this version of the standard an IE container list may contain only one kind of list elements. 

If a RANAP message that is not constructed as defined above is received, this shall be considered as Abstract Syntax Error, and the message shall be handled as defined for 
Abstract Syntax Error in subclause 10.3.6. 

Subclause 9.3 presents the Abstract Syntax of RANAP protocol with ASN.l. In case there is contradiction between the ASN.l definition in this subclause and the tabular format 
in subclause 9.1 and 9.2, the ASN.l shall take precedence, except for the definition of conditions for the presence of conditional elements, where the tabular format shall take 
precedence. 

9.3.1 Usage of private message mechanism for non-standard use 

The private message mechanism for non-standard use may be used: 

for special operator- (and/or vendor) specific features considered not to be part of the basic functionality, i.e. the functionality required for a complete and high-quality 
specification in order to guarantee multivendor interoperabihty; 

- by vendors for research purposes, e.g. to implement and evaluate new algorithms/features before such features are proposed for standardisation. 

The private message mechanism shall not be used for basic functionality. Such functionality shall be standardised. 

9.3.2 Elementary Procedure Definitions 

************************************************************** 

— Elementary Procedure definitions 

£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



127 



ETSI TS 125 413 V4.10.0 (2003-09) 



************************************************************** 

RANAP-PDU-Descriptions ( 

itu-t (0) identif ied-organization (4) etsi (0) mobileDomain (0) 

umts-Access (20) modules (3) ranap (0) versionl (1) ranap-PDU-Descriptions (0) } 

DEFINITIONS AUTOMATIC TAGS ::= 

BEGIN 

************************************************************** 

— IE parameter types from other modules . 

************************************************************** 

IMPORTS 

Criticality, 

ProcedureCode 
FROM RANAP-CommonDataTypes 

lu-ReleaseCommand, 

lu-ReleaseComplete, 

RelocationCommand, 

RelocationPreparationFailure, 

RelocationRequired, 

RelocationRequest, 

RelocationRequestAcknowledge, 

RelocationFailure, 

RelocationCancel, 

Re locationCan eel Acknowledge, 

SRNS-ContextRequest, 

SRNS-Context Response, 

SecurityModeCommand, 

SecurityModeComplete, 

Secur ItyModeRe j ect , 

DataVolumeReportRequest, 

DataVolumeReport , 

Reset, 

Re set Acknowledge, 

RAB-ReleaseRequest, 

lu-ReleaseRequest, 

RelocationDetect, 

RelocationComplete, 

Paging, 

CommonID, 

CN-InvokeTrace, 

CN-DeactivateTrace, 

LocationReportingControl, 

LocationReport , 

InitialUE-Message, 

DirectTransfer, 

Overload, 

Errorlndication, 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



128 



ETSI TS 125 413 V4.10.0 (2003-09) 



SRNS-DataForwardCommand, 
ForwardSRNS-Context, 
RAB-AssignmentRequest, 
RAB-AssignmentResponse, 
RAB-ModifyRequest, 
PrivateMessage, 
Re set Re source, 
Re set Re source Acknowledge, 
RANAP-Re location Information, 
LocationRelatedDataRequest, 
LocationRelatedDataResponse, 
LocationRelatedDataFailure 
FROM RANAP-PDU-Contents 

Id-LocationRelatedData, 
id-CN-DeactivateTrace, 
id-CN-InvokeTrace, 
id-CommonID, 
id-DataVolumeReport , 
id-DirectXransfer, 
id-Err or Indication, 
id-ForwardSRNS-Context, 
id- I nitialUE -Message, 
id-Iu-Release, 
id-Iu-ReleaseRequest , 
id-LocationReport, 
id-LocationReportingControl, 
id-OverloadControl, 
id-Paging, 
id-privateMessage, 
id-RAB-Assignment, 
id-RAB-ReleaseRequest, 
id-RAB-ModifyRequest, 
id-RANAP-Re location, 
id-Re locationCancel, 
id-RelocationComplete, 
id-Re locationDetect, 
id-Re locationP reparation, 
id-RelocationRe source Alio cat ion, 
id-Reset, 

id-SRNS-ContextTransfer, 
id-SRNS-DataForward, 
Id-SecurityModeControl, 
id-Re set Re source 
FROM RANAP-Constants; 

************************************************************** 

— Interface Elementary Procedure Class 

************************************************************** 



RANAP-ELEMENTARY-PROCEDURE 
&InitiatingMessage 



CLASS { 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



129 



ETSI TS 125 413 V4.10.0 (2003-09) 



& Success fulOut come 
SUnsuccessf ulOutcome 
SOutcome 
SprocedureCode 
Scriticality 



OPTIONAL, 

OPTIONAL, 
OPTIONAL, 
ProcedureCode UNIQUE, 
Criticality DEFAULT ignore 



WITH SYNTAX ( 

INITIATING MESSAGE & InitiatingMessage 

[SUCCESSFUL OUTCOME SSuccessf ulOutcome ] 

[UNSUCCESSFUL OUTCOME SUnsuccessf ulOutcome ] 

[OUTCOME SOutcome] 

PROCEDURE CODE SprocedureCode 

[CRITICALITY Scriticality ] 



************************************************************** 



— Interface PDU Definition 



************************************************************** 



RANAP-PDU ::= CHOICE { 

initiatingMessage InitiatingMessage, 
success f ulOutcome Success f ulOutcome, 
unsuccessf ulOutcome Unsuccessf ulOutcome, 
outcome Outcome, 



InitiatingMessage ::= SEQUENCE { 

procedureCode RANAP-ELEMENTARY-PROCEDURE . SprocedureCode ( ( RANAP-ELEMENTARY-PROCEDURES } ) , 
criticality RANAP-ELEMENTARY-PROCEDURE . Scriticality ({RANAP-ELEMENTARY-PROCEDURES} ( gprocedureCode } ) , 
value RANAP-ELEMENTARY-PROCEDURE.& InitiatingMessage ( (RANAP-ELEMENTARY-PROCEDURES) { gprocedureCode } ) 

} 

SuccessfulOutcome ::= SEQUENCE { 

procedureCode RANAP-ELEMENTARY-PROCEDURE . SprocedureCode ((RANAP-ELEMENTARY-PROCEDURES}) , 
criticality RANAP-ELEMENTARY-PROCEDURE . Scriticality ((RANAP-ELEMENTARY-PROCEDURES) ( gprocedureCode } ) , 
value RANAP-ELEMENTARY-PROCEDURE. SSuccessf ulOutcome ( (RANAP-ELEMENTARY-PROCEDURES) ( gprocedureCode } ) 

) 

UnsuccessfulOutcome ::= SEQUENCE ( 

procedureCode RANAP-ELEMENTARY-PROCEDURE . SprocedureCode ((RANAP-ELEMENTARY-PROCEDURES)) , 
criticality RANAP-ELEMENTARY-PROCEDURE . Scriticality ((RANAP-ELEMENTARY-PROCEDURES) ( gprocedureCode ) ) , 
value RANAP-ELEMENTARY-PROCEDURE . SUnsuccessf ulOutcome ( ( RANAP-ELEMENTARY-PROCEDURES ) ( gprocedureCode ) ) 

) 

Outcome ;;= SEQUENCE ( 

procedureCode RANAP-ELEMENTARY-PROCEDURE . SprocedureCode ((RANAP-ELEMENTARY-PROCEDURES)) , 
criticality RANAP-ELEMENTARY-PROCEDURE . Scriticality ((RANAP-ELEMENTARY-PROCEDURES) (SprocedureCode)) , 
value RANAP-ELEMENTARY-PROCEDURE . SOutcome ( ( RANAP-ELEMENTARY-PROCEDURES ) ( gprocedureCode ) ) 

) 

************************************************************** 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



130 



ETSI TS 125 413 V4.10.0 (2003-09) 



— Interface Elementary Procedure List 

************************************************************** 

RANAP-ELEMENTARY-PROCEDURES RANAP-ELEMENTARY-PROCEDURE :;= { 
RANAP-ELEMENTARY-PROCEDURES-CLASS-1 I 
RANAP-ELEMENTARY-PROCEDURES-CLASS-2 | 
RANAP-ELEMENTARY-PROCEDURES-CLASS-3 , 



RANAP-ELEMENTARY-PROCEDURES-CLASS-1 RANAP-ELEMENTARY-PROCEDURE 
iu-Release I 

relocationPreparation | 
relocationResourceAllocation | 



relocationCancel 
sRNS-ContextTransfer 
securityModeControl 
dataVolume Report 
reset I 
reset Re source 



I 



I 



locationRelatedData 



RANAP-ELEMENTARY-PROCEDURES-CLASS-2 RANAP-ELEMENTARY-PROCEDURE 

rAB-ReleaseRequest I 

iu-ReleaseRequest | 

relocationDetect | 

relocationComplete I 

paging | 

common ID | 

cN-InvokeTrace I 

cN-DeactivateTrace I 
locationReportingControl | 

locationReport | 

initialUE -Message | 

directTransfer | 

overloadControl I 

errorlndication | 

sRNS-DataForward I 

forwardSRNS-Context I 

privateMessage I 

rANAP-Relocation , 



rAB-Modify Request 



RANAP-ELEMENTARY-PROCEDURES-CLASS-3 RANAP-ELEMENTARY-PROCEDURE 
rAB-Assignment , 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



131 



ETSI TS 125 413 V4.10.0 (2003-09) 



************************************************************** 



Interface Elementary Procedures 



************************************************************** 



iu-Release RANAP-ELEMENTARY-PROCEDURE ;;= { 
INITIATING MESSAGE lu-ReleaseCommand 
SUCCESSFUL OUTCOME lu-ReleaseComplete 
PROCEDURE CODE id-Iu-Release 
CRITICALITY reject 



relocationPreparation RANAP-ELEMENTARY-PROCEDURE ::= { 
INITIATING MESSAGE RelocationRequired 
SUCCESSFUL OUTCOME RelocationCommand 

UNSUCCESSFUL OUTCOME RelocationPreparationFailure 
PROCEDURE CODE id-RelocationPreparation 

CRITICALITY reject 



relocationResourceAllocation RANAP-ELEMENTARY-PROCEDURE ::= 
INITIATING MESSAGE RelocationRequest 
SUCCESSFUL OUTCOME RelocationRequestAcknowledge 
UNSUCCESSFUL OUTCOME RelocationFailure 

PROCEDURE CODE Id-RelocationResourceAllocation 

CRITICALITY reject 



relocationCancel RANAP-ELEMENTARY-PROCEDURE ::= { 
INITIATING MESSAGE RelocationCancel 
SUCCESSFUL OUTCOME RelocationCancelAcknowledge 
PROCEDURE CODE id-RelocationCancel 
CRITICALITY reject 



sRNS-ContextTransfer RANAP-ELEMENTARY-PROCEDURE 
INITIATING MESSAGE SRNS-ContextRequest 
SUCCESSFUL OUTCOME SRNS-ContextResponse 
PROCEDURE CODE Id-SRNS-ContextTransf er 
CRITICALITY reject 



securityModeControl RANAP-ELEMENTARY-PROCEDURE 
INITIATING MESSAGE SecurityModeCommand 
SUCCESSFUL OUTCOME SecurityModeComplete 
UNSUCCESSFUL OUTCOME SecurityModeRe ject 
PROCEDURE CODE Id-SecurityModeControl 
CRITICALITY reject 



dataVolumeReport RANAP-ELEMENTARY-PROCEDURE ::= { 
INITIATING MESSAGE DataVolumeReportRequest 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



132 



ETSI TS 125 413 V4.10.0 (2003-09) 



SUCCESSFUL OUTCOME DataVolumeReport 
PROCEDURE CODE id-DataVolumeReport 
CRITICALITY reject 



reset RANAP-ELEMENTARY-PROCEDURE ::= { 
INITIATING MESSAGE Reset 
SUCCESSFUL OUTCOME ResetAcknowledge 
PROCEDURE CODE id-Reset 
CRITICALITY reject 



rAB-ReleaseRequest RANAP-ELEMENTARY-PROCEDURE 
INITIATING MESSAGE RAB-ReleaseRequest 
PROCEDURE CODE id-RAB-ReleaseRequest 
CRITICALITY ignore 



iu-ReleaseRequest RANAP-ELEMENTARY-PROCEDURE 
INITIATING MESSAGE lu-ReleaseRequest 
PROCEDURE CODE id-Iu-ReleaseRequest 
CRITICALITY ignore 



relocationDetect RANAP-ELEMENTARY-PROCEDURE 
INITIATING MESSAGE RelocationDetect 
PROCEDURE CODE id-RelocationDetect 
CRITICALITY ignore 



relocationComplete RANAP-ELEMENTARY-PROCEDURE 
INITIATING MESSAGE RelocationComplete 
PROCEDURE CODE id-RelocationComplete 
CRITICALITY ignore 

} 



paging RANAP-ELEMENTARY-PROCEDURE 
INITIATING MESSAGE Paging 
PROCEDURE CODE id-Paging 
CRITICALITY ignore 



{ 



commonID RANAP-ELEMENTARY-PROCEDURE 
INITIATING MESSAGE CommonID 
PROCEDURE CODE id-CommonID 
CRITICALITY ignore 



cN-InvokeTrace RANAP-ELEMENTARY-PROCEDURE 
INITIATING MESSAGE CN-InvokeTrace 
PROCEDURE CODE id-CN-InvokeTrace 
CRITICALITY ignore 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



133 



ETSI TS 125 413 V4.10.0 (2003-09) 



cN-DeactivateTrace RANAP-ELEMENTARY-PROCEDURE ::= 
INITIATING MESSAGE CN-DeactivateTrace 
PROCEDURE CODE id-CN-DeactivateTrace 

CRITICALITY ignore 



locationReportingControl RANAP-ELEMENTARY-PROCEDURE 
INITIATING MESSAGE LocationReportingControl 
PROCEDURE CODE id-LocationReportingControl 
CRITICALITY ignore 



locationReport RANAP-ELEMENTARY-PROCEDURE 
INITIATING MESSAGE LocationReport 
PROCEDURE CODE id-LocationReport 
CRITICALITY ignore 



initialUE-Message RANAP-ELEMENTARY-PROCEDURE 
INITIATING MESSAGE InitialUE-Message 
PROCEDURE CODE id-InitialUE-Message 
CRITICALITY ignore 



directTransfer RANAP-ELEMENTARY-PROCEDURE : 
INITIATING MESSAGE DirectTransfer 
PROCEDURE CODE id-DirectTransf er 
CRITICALITY ignore 

} 

overloadControl RANAP-ELEMENTARY-PROCEDURE 
INITIATING MESSAGE Overload 
PROCEDURE CODE id-OverloadControl 
CRITICALITY ignore 



error Indication RANAP-ELEMENTARY-PROCEDURE 
INITIATING MESSAGE Error Indication 
PROCEDURE CODE id-Error Indication 
CRITICALITY ignore 



sRNS-DataForward RANAP-ELEMENTARY-PROCEDURE ::= { 
INITIATING MESSAGE SRNS-DataForwardCommand 
PROCEDURE CODE Id-SRNS-DataForward 
CRITICALITY ignore 



forwardSRNS-Context RANAP-ELEMENTARY-PROCEDURE 
INITIATING MESSAGE ForwardSRNS-Context 
PROCEDURE CODE id-ForwardSRNS-Context 
CRITICALITY ignore 



} 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



134 



ETSI TS 125 413 V4.10.0 (2003-09) 



rAB-Assignment RANAP-ELEMENTARY-PROCEDURE ::= { 
INITIATING MESSAGE RAB-AssignmentRequest 
OUTCOME RAB-AssignmentResponse 
PROCEDURE CODE id-RAB-Assignment 
CRITICALITY reject 



privateMessage RANAP-ELEMENTARY-PROCEDURE ::= { 
INITIATING MESSAGE PrivateMessage 

PROCEDURE CODE id-privateMessage 
CRITICALITY ignore 



resetResource RANAP-ELEMENTARY-PROCEDURE ::= { 
INITIATING MESSAGE ResetResource 
SUCCESSFUL OUTCOME ResetResourceAcknowledge 
PROCEDURE CODE id-ResetResource 

CRITICALITY reject 



rANAP-Relocation RANAP-ELEMENTARY-PROCEDURE : := ( 

INITIATING MESSAGE RANAP-RelocationInf ormation 
PROCEDURE CODE id-RANAP-Relocation 

CRITICALITY ignore 



rAB-ModifyRequest RANAP-ELEMENTARY-PROCEDURE ::= { 
INITIATING MESSAGE RAB-ModifyRequest 
PROCEDURE CODE id-RAB-Modif yRequest 
CRITICALITY ignore 



locationRelatedData RANAP-ELEMENTARY-PROCEDURE 



{ 



INITIATING MESSAGE 
SUCCESSFUL OUTCOME 
UNSUCCESSFUL OUTCOME 
PROCEDURE CODE 
CRITICALITY 



LocationRelatedDataRequest 
LocationRelatedDataResponse 
LocationRelatedDataFailure 
id-LocationRelatedData 

reject 



9.3.3 PDU Definitions 



************************************************************** 



PDU definitions for RANAP . 



************************************************************** 



RANAP-PDU-Contents { 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



135 



ETSI TS 125 413 V4.10.0 (2003-09) 



itu-t (0) identif ied-organization (4) etsi (0) mobileDomain (0) 

umts-Access (20) modules (3) ranap (0) versionl (1) ranap-PDU-Contents (1) } 

DEFINITIONS AUTOMATIC TAGS ::= 

BEGIN 

************************************************************** 

— IE parameter types from other modules . 

************************************************************** 

IMPORTS 

BroadcastAssistanceDataDecipheringKeys, 

LocationRelatedDataRequestType, 

DataVolumeReference, 

Arealdentity, 

CN-Domain Indicator, 

Cause, 

ClientType, 

CriticalityDiagnostics, 

ChosenEncryptionAlgorithm, 

ChosenlntegrityProtectionAlgorithm, 

Classmarklnf ormation2 , 

Classmark Informations, 

DL-GTP-PDU-SequenceNumber, 

DL-N-PDU-SequenceNumber, 

DataVolumeReportinglndication, 

DRX-CycleLengthCoef f icient. 

Encrypt ionlnformat ion, 

GlobalCN-ID, 

GlobalRNC-ID, 

IntegrityProtect ionlnformat ion, 

luSignallingConnect ion Identifier, 

luTransportAssociation, 

KeyStatus, 

L3-Inf ormation, 

LAI, 

LastKnownServiceArea, 

NAS-PDU, 

NAS-Synchroni sat ion Indicator, 

NonSearchinglndication, 

NumberOf Steps, 

OMC-ID, 

OldBSS-ToNewBSS-Inf ormation, 

PagingArealD, 

PagingCause, 

PDP-Type Information, 

PermanentNAS-UE-ID, 

PositioningPriority, 

RAB-ID, 

RAB-Parameters, 

RAG, 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



136 



ETSI TS 125 413 V4.10.0 (2003-09) 



RelocationType, 
RequestType, 

Requested-RAB-Parameter-Values, 
ResponseTime , 
SAI, 
SAP I, 

Service -Handover, 
SourcelD, 

Sour ceRNC-ToTargetRNC-Transparent Container, 
TargetID, 

Tar getRNC-ToSourceRNC-Transparent Container, 
TemporaryUE-ID, 
TraceReference, 
TraceType, 

Unsuccessf ullyTransmittedDataVolume, 
TransportLayerAddress, 
TriggerlD, 
UE-ID, 

UL-GTP-PDU-SequenceNumber, 
UL-N-PDU-SequenceNumber, 
UP-ModeVersions, 
UserPlaneMode, 
Vert icalAccuracy Code, 
Alt-RAB-Parameters, 
Ass-RAB-Parameters 
FROM RANAP-IEs 



PrivatelE-Container { } , 
ProtocolExtensionContainer { } , 
ProtocolIE-ContainerList { } , 
ProtocolIE-ContainerPair { } , 
ProtocolIE-ContainerPairList ( } , 
ProtocolIE-Container { } , 
RANAP-PRIVATE-IES, 
RANAP-PROTOCOL-EXTENS I ON , 
RANAP-PROTOCOL-IES, 
RANAP-PROTOCOL-IES-PAIR 
FROM RANAP-Containers 

maxNrOfDTs, 
maxNr Of Errors, 
maxNrOf luSigConlds, 
maxNrOfRABs, 
maxNrOfVol, 

id-Arealdentity, 

id-Alt-RAB-Parameters, 

id-Ass-RAB-Parameters, 

id-Broadcast As sistanceDataDecipheringKeys, 

id-LocationRelatedDataRequestType, 

id-CN-Domain Indicator, 

id-Cause, 

id-ChosenEncryptionAlgorithm, 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



137 



ETSI TS 125 413 V4.10.0 (2003-09) 



id-ChosenlntegrityProtectionAlgorithm, 

id-ClassmarkInf ormation2 , 

id-ClassmarkInf ormationS, 

id-Client Type, 

id-CriticalityDiagnostics, 

id-DRX-CycleLengthCoef f icient , 

id-DirectTransf er Information! tem-RANAP-RelocInf, 

id-DirectTransf erinf ormationList-RANAP-RelocInf , 

id-DL-GTP-PDU-SequenceNumber, 

id-Encrypt ionlnformat ion, 

id-GlobalCN-ID, 

id-GlobalRNC-ID, 

id-IntegrityProtect ionlnformat ion, 

id-IuSigConId, 

id-IuSigConldltem, 

id-IuSigConldList , 

id-IuTransportAssociation, 

id-KeyStatus, 

id-L3-Inf ormation, 

id- LAI, 

id-LastKnownServiceArea, 

id-NAS-PDU, 

id-NonSearchinglndication, 

id-NumberOf Steps, 

id-OMC-ID, 

id-OldBSS-ToNewBSS-Inf ormation, 

id-PagingArealD, 

id-PagingCause, 

id-PermanentNAS-UE-ID, 

id-PositioningPriority, 

id-RAB-Contextltem, 

id-RAB-ContextList, 

id-RAB-ContextFailedtoTransferltem, 

id-RAB-ContextFailedtoTransferList, 

id-RAB-Contextltem-RANAP-RelocInf , 

id-RAB-ContextList-RANAP-RelocInf , 

id-RAB-DataForwardingltem, 

id-RAB-DataForwardingltem-SRNS-CtxReq, 

id-RAB-DataForwardingList, 

id-RAB-DataForwardingList-SRNS-CtxReq, 

id-RAB-DataVolumeReportltem, 

id-RAB-DataVolumeReportList, 

id-RAB-DataVolumeReportRequestltem, 

Id-RAB-DataVolumeReportRequestList, 

id-RAB-Failedltem, 

id-RAB-FailedList, 

id-RAB-FailedtoReportltem, 

id-RAB-FailedtoReportList, 

id-RAB-ID, 

id-RAB-ModifyList, 

id-RAB-Modifyltem, 

id-RAB-Queuedltem, 

id-RAB-QueuedList, 

id-RAB-ReleaseFailedList, 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



138 



ETSI TS 125 413 V4.10.0 (2003-09) 



id-RAB-Re lease I tern, 
id-RAB-Releasedltem-IuRelComp, 
id-RAB-ReleaseList, 
id-RAB-Re leasedlt em, 
id-RAB-ReleasedList, 
id-RAB-Re leasedList-IuRelComp, 
id-RAB-Re locationRelease It em, 
id-RAB-Re locationReleaseLi St, 
id-RAB-SetupItem-RelocReq, 
id-RAB-SetupItem-RelocReqAck, 
id-RAB-SetupList-RelocReq, 
id-RAB-SetupList-RelocReqAck, 
id-RAB-SetupOrModifiedltem, 
id-RAB-SetupOrModifiedList, 
id-RAB-SetupOrModifyltem, 
id-RAB-SetupOrModifyList, 
id-RAC, 

id-RelocationType, 
id-RequestType , 
id-ResponseTime , 
id-SAI, 
id-SAPI, 
id-SourcelD, 

id-Sour ceRNC-ToTargetRNC-Transparent Container, 
id-TargetID, 

id-Tar getRNC-ToSourceRNC-Transparent Container, 
id-TemporaryUE-ID, 
id-TraceReference, 
id-TraceType, 
id-TransportLayerAddress, 
id-Trigger ID, 
id-UE-ID, 

id-UL-GTP-PDU-SequenceNumber, 
id-Vert icalAccuracyCode 
FROM RANAP-Constants; 



************************************************************** 



Common Container Lists 



************************************************************** 



RAB- IE -Container Li St 

} 

RAB- IE -Container Pair Li St 

} 

ProtocolError-IE-ContainerList 



{ RANAP-PROTOCOL-IES 

{ RANAP-PROTOCOL-IES-PAIR 

{ RANAP-PROTOCOL-IES 

{ RANAP-PROTOCOL-IES 



I uSigCon Id- IE -Container List 

{lEsSetParam} } 

DirectTransfer-IE-ContainerList { RANAP-PROTOCOL-IES 



lEsSetParam } 
lEsSetParam } 
lEsSetParam } 
lEsSetParam } 



ProtocolIE-ContainerList { 1, maxNrOfRABs, 
ProtocolIE-ContainerPairList ( 1, maxNrOfRABs, 
ProtocolIE-ContainerList ( 1, maxNrOfRABs, 



{ LEsSetParam} 
( lEsSetParam} 
( lEsSetParam} 



lEsSetParam } 



ProtocolIE-ContainerList ( 1, maxNrOf luSigConlds, 
ProtocolIE-ContainerList { 1, maxNrOfDTs, {LEsSetParam} } 



************************************************************** 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



139 



ETSI TS 125 413 V4.10.0 (2003-09) 



— lu RELEASE ELEMENTARY PROCEDURE 



************************************************************** 

************************************************************** 



lu Release Command 



************************************************************** 



lu-ReleaseCommand ::= SEQUENCE { 

protocolIEs ProtocolIE-Container ( ( lu-ReleaseCommandlEs } }, 

protocolExtensions ProtocolExtensionContainer { { lu-ReleaseCommandExtensions } } 



OPTIONAL, 



lu-ReleaseCommandlEs RANAP-PROTOCOL-IES ::= { 

{ ID id-Cause CRITICALITY ignore TYPE Cause 



PRESENCE mandatory } , 



lu-ReleaseCommandExtensions RANAP-PROTOCOL-EXTENSION ;;= { 

} 

************************************************************** 

— lu Release Complete 

************************************************************** 



lu-ReleaseComplete ::= SEQUENCE { 

protocolIEs ProtocolIE-Container { ( lu-ReleaseCompletelEs } }, 
protocolExtensions ProtocolExtensionContainer ( ( lu-ReleaseCompleteExtensions } } 



OPTIONAL, 



lu-ReleaseCompletelEs RANAP-PROTOCOL-IES 
( ID Id-RAB-DataVolumeReportList 
{ ID id-RAB-ReleasedList-IuRelComp 
{ ID Id-CriticalityDiagnostics 



= { 

CRITICALITY ignore TYPE RAB-DataVolumeReportList 

CRITICALITY ignore TYPE RAB-ReleasedList-IuRelComp 

CRITICALITY ignore TYPE CriticalityDiagnostics 



PRESENCE optional } 
PRESENCE optional } 
PRESENCE optional }, 



RAB-DataVolumeReportList 



RAB-IE-ContainerLlst ( ( RAB-DataVolumeReportltemlEs } } 



RAB-DataVolumeReportltemlEs RANAP-PROTOCOL-IES ::= { 

( ID Id-RAB-DataVolumeReportltem CRITICALITY ignore TYPE RAB-DataVolumeReportltem 



PRESENCE mandatory }, 



RAB-DataVolumeReportltem ::= SEQUENCE { 
rAB-ID RAB-ID, 

dl-Unsuccessf ullyTransmittedDataVolume 



DataVolumeLlst 



OPTIONAL 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



140 



ETSI TS 125 413 V4.10.0 (2003-09) 



— This IE shall always be present although its presence is optional — , 

IE-Extensions ProtocolExtensionContainer { { RAB-DataVolumeReportltem-ExtlEs } } 



} 



OPTIONAL, 



RAB-DataVolumeReportltem-ExtlEs RANAP-PROTOCOL-EXTENSION ;;= { 

} 

RAB-ReleasedList-IuRelComp ;:= RAB-IE-ContainerList { { RAB-Releasedltem-IuRelComp-IEs } } 

RAB-Releasedltem-IuRelComp-IEs RANAP-PROTOCOL-IES ::= ( 

( ID id-RAB-Releasedltem-IuRelComp CRITICALITY ignore TYPE RAB-Releasedltem-IuRelComp 



PRESENCE mandatory 



RAB-Releasedltem-IuRelComp ::= SEQUENCE { 
rAB-ID RAB-ID, 

dL-GTP-PDU-SequenceNumber DL-GTP-PDU-SequenceNumber OPTIONAL, 
uL-GTP-PDU-SequenceNumber UL-GTP-PDU-SequenceNumber OPTIONAL, 
IE-Extensions ProtocolExtensionContainer { { RAB-Releasedltem-IuRelComp-ExtlEs } } 



OPTIONAL, 



RAB-Releasedltem-IuRelComp-ExtlEs RANAP-PROTOCOL-EXTENSION ::= { 



lu-ReleaseCompleteExtensions RANAP-PROTOCOL-EXTENSION ::= { 



************************************************************** 



— RELOCATION PREPARATION ELEMENTARY PROCEDURE 

************************************************************** 



************************************************************** 



— Relocation Required 



************************************************************** 



RelocationRequired ::= SEQUENCE ( 

protocolIEs ProtocolIE-Container ( { RelocationRequiredlEs } }, 

protocolExtensions ProtocolExtensionContainer { { RelocationRequiredExtensions } 



OPTIONAL, 



RelocationRequiredlEs RANAP-PROTOCOL-IES ::= { 

{ ID Id-RelocationType CRITICALITY reject TYPE RelocationType 

{ ID id-Cause CRITICALITY ignore TYPE Cause 



PRESENCE mandatory 
PRESENCE mandatory } | 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



141 



ETSI TS 125 413 V4.10.0 (2003-09) 



{ ID id-SourcelD CRITICALITY ignore TYPE SourcelD PRESENCE mandatory } | 

{ ID id-TargetID CRITICALITY reject TYPE TargetID PRESENCE mandatory } | 

{ ID id-ClassmarkInformation2 CRITICALITY reject TYPE Classmarklnf ormation2 PRESENCE conditional 

— This IE shall be present if the Target ID IE contains a CGI IE — } 

{ ID id-ClassmarkInformation3 CRITICALITY ignore TYPE Classmarklnf ormationS PRESENCE conditional 

— This IE shall be present if the Target ID IE contains a CGI IE — } 
{ ID Id-SourceRNC-ToTargetRNC-TransparentContainer 

CRITICALITY reject TYPE SourceRNC-ToTargetRNC-TransparentContainer PRESENCE conditional 

— This IE shall be present if the Target ID IE contains a RNC-ID IE — } 

{ ID id-OldBSS-ToNewBSS-Information CRITICALITY ignore TYPE OldBSS-ToNewBSS-Inf ormation PRESENCE optional 



RelocationRequiredExtensions RANAP-PROTOCOL-EXTENSION ::= { 

} 

************************************************************** 



Relocation Command 



************************************************************** 



RelocationCommand ::= SEQUENCE { 

protocolIEs ProtocolIE-Container { ( RelocationCommandlEs } }, 

protocolExtensions ProtocolExtensionContainer { { RelocationCommandExtensions } } 



OPTIONAL, 



} 



RelocationCommandlEs RANAP-PROTOCOL-IES ::= { 

( ID Id-TargetRNC-ToSourceRNC-TransparentContainer 

CRITICALITY reject TYPE TargetRNC-ToSourceRNC-TransparentContainer PRESENCE optional 



{ ID id-L3-Inf ormation 

{ ID id-RAB-RelocationReleaseList 

{ ID Id-RAB-DataForwardingList 

{ ID Id-CriticalityDiagnostics 



CRITICALITY ignore TYPE L3-Inf ormation PRESENCE optional } I 

CRITICALITY ignore TYPE RAB-RelocationReleaseList PRESENCE optional } 
CRITICALITY ignore TYPE RAB-DataForwardingList PRESENCE optional } 
CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }, 



RAB-RelocationReleaseList 



RAB-IE-ContainerList ( ( RAB-RelocationReleaseltemlEs } } 



RAB-RelocationReleaseltemlEs RANAP-PROTOCOL-IES ::= ( 

{ ID Id-RAB-RelocationReleaseltem CRITICALITY ignore TYPE RAB-RelocationReleaseltem 



PRESENCE mandatory }, 



RAB-RelocationReleaseltem 
rAB-ID 
iE-Extensions 



SEQUENCE { 
RAB-ID, 

ProtocolExtensionContainer { { RAB-RelocationReleaseltem-ExtlEs } } 



OPTIONAL, 



RAB-RelocationReleaseltem-ExtlEs RANAP-PROTOCOL-EXTENSION 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 142 ETSI TS 125 413 V4.10.0 (2003-09) 

} 

RAB-DataForwardingList ::= RAB-IE-ContainerList { { RAB-DataForwardingltemlEs } } 

RAB-DataForwardingltemlEs RANAP-PROTOCOL-IES ::= ( 

( ID id-RAB-DataForwardingltem CRITICALITY ignore TYPE RAB-DataForwardingltem PRESENCE mandatory }, 

} 

RAB-DataForwardingltem ::= SEQUENCE { 

rAB-ID RAB-ID, 

transportLayerAddress TransportLayerAddress, 

iuTransportAssociation luTransportAssociation, 

iE-Extensions ProtocolExtensionContainer ( ( RAB-DataForwardingltem-ExtlEs } } OPTIONAL, 

} 

RAB-DataForwardingltem-ExtlEs RANAP-PROTOCOL-EXTENSION ::= { 

} 

RelocationCommandExtensions RANAP-PROTOCOL-EXTENSION ;;= { 

} 

************************************************************** 

— Relocation Preparation Failure 

************************************************************** 

RelocationPreparationFailure : := SEQUENCE { 

protocolIEs ProtocolIE-Container { { RelocationPreparationFailurelEs } }, 

protocolExtensions ProtocolExtensionContainer { ( RelocationPreparationFailureExtensions } } OPTIONAL, 

} 

RelocationPreparationFailurelEs RANAP-PROTOCOL-IES ::= { 

( ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory } | 

( ID Id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }, 

} 

RelocationPreparationFailureExtensions RANAP-PROTOCOL-EXTENSION ::= { 

} 

************************************************************** 

— RELOCATION RESOURCE ALLOCATION ELEMENTARY PROCEDURE 

************************************************************** 

************************************************************** 

£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



143 



ETSI TS 125 413 V4.10.0 (2003-09) 



— Relocation Request 



************************************************************** 



RelocationRequest ::= SEQUENCE { 

protocolIEs ProtocolIE-Container { { RelocationRequestlEs } }, 

protocolExtensions ProtocolExtensionContainer { ( RelocationRequestExtensions } } 



OPTIONAL, 



RelocationRequestlEs RANAP-PROTOCOL-IES ::= { 

( ID Id-PermanentNAS-UE-ID CRITICALITY ignore TYPE PermanentNAS-UE-ID PRESENCE optional } 

{ ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory } | 

{ ID id-CN-Domainlndicator CRITICALITY reject TYPE CN-Domainlndicator PRESENCE mandatory } 

{ ID Id-SourceRNC-ToTargetRNC-TransparentContainer 

CRITICALITY reject TYPE SourceRNC-ToTargetRNC-TransparentContainer PRESENCE mandatory } 
{ ID id-RAB-SetupList-RelocReq CRITICALITY reject TYPE RAB-SetupList-RelocReq PRESENCE optional } 

{ ID id-IntegrityProtectionlnformation CRITICALITY ignore TYPE IntegrityProtectionInf ormation PRESENCE optional } I 
{ ID id-Encryptionlnformation CRITICALITY ignore TYPE Encryptioninf ormation PRESENCE optional } 

{ ID id-IuSigConId CRITICALITY ignore TYPE luSignallingConnectionldentlf ier PRESENCE mandatory }, 



RAB-SetupList-RelocReq 



RAB-IE-ContainerLlst ( { RAB-SetupItem-RelocReq-IEs } } 



RAB-SetupItem-RelocReq-IEs RANAP-PROTOCOL-IES ::= { 

{ ID id-RAB-SetupItem-RelocReq CRITICALITY reject 



TYPE RAB-SetupItem-RelocReq 



PRESENCE mandatory }, 



RAB-Se tup It em-Re locReq 
rAB-ID 



SEQUENCE { 

RAB-ID, 



nAS-Synchroni sat ion Indicator 

rAB-Parameters 

dataVolumeReportinglndication 

— This IE shall be present if 
pDP-Type Information 

— This IE shall be present if 
userPlane Information 
transportLayerAddress 
iuTransportAssociation 
service -Handover 
iE-Extensions 



NAS-Synchroni sat ion Indicator OPTIONAL, 
RAB-Parameters, 

DataVolumeReportinglndication OPTIONAL 
the CM domain Indicator IE is set to "PS domain" — , 

PDP-Typelnformation OPTIONAL 
the CM domain Indicator IE is set to "PS domain" — , 
UserPlane Information, 
TransportLayerAddress, 
IuTransportAssociation, 
Service-Handover OPTIONAL, 
ProtocolExtensionContainer ( ( RAB-SetupItem-RelocReq-ExtlEs } } 



OPTIONAL, 



RAB-SetupItem-RelocReq-ExtlEs RANAP-PROTOCOL-EXTENSION ::= { 

— Extension for Release 4 to enable RAB Quality of Service negotiation over lu — 

{ID id-Alt-RAB-Parameters CRITICALITY ignore EXTENSION Alt-RAB-Parameters 



PRESENCE optional}, 



UserPlane Information 



SEQUENCE { 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 144 ETSI TS 125 413 V4.10.0 (2003-09) 

userPlaneMode UserPlaneMode, 

uP-ModeVersions UP-ModeVersions, 

iE-Extensions ProtocolExtensionContainer { { UserPlaneInf ormation-ExtlEs } } OPTIONAL, 

} 

UserPlanelnformation-ExtlEs RANAP-PROTOCOL-EXTENSION ::= { 
} 

RelocationRequestExtensions RANAP-PROTOCOL-EXTENSION ::= { 

— Extension for Release 4 — 

( ID id-GlobalCN-ID CRITICALITY reject EXTENSION GlobalCN-ID PRESENCE optional}, 

} 

************************************************************** 

— Relocation Request Acknowledge 

************************************************************** 

RelocationRequestAcknowledge : := SEQUENCE ( 

protocolIEs ProtocolIE-Container ( ( RelocationRequestAcknowledgelEs } }, 

protocolExtensions ProtocolExtensionContainer { { RelocationRequestAcknowledgeExtensions } } OPTIONAL, 

} 

RelocationRequestAcknowledgelEs RANAP-PROTOCOL-IES ::= { 
{ ID Id-TargetRNC-ToSourceRNC-TransparentContainer 

CRITICALITY ignore TYPE TargetRNC-ToSourceRNC-TransparentContainer PRESENCE optional } 
{ ID Id-RAB-SetupList-RelocReqAck CRITICALITY ignore TYPE RAB-SetupList-RelocReqAck PRESENCE optional} 
{ ID Id-RAB-FailedList CRITICALITY ignore TYPE RAB-FailedList PRESENCE optional } I 

{ ID Id-ChosenlntegrityProtectionAlgorithm CRITICALITY ignore TYPE ChosenlntegrityProtectionAlgorithm PRESENCE optional } 
{ ID Id-ChosenEncryptionAlgorithm CRITICALITY ignore TYPE ChosenEncryptionAlgorithm PRESENCE optional } 
{ ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }, 

} 

RAB-SetupList-RelocReqAck :;= RAB-IE-ContainerList ( ( RAB-SetupItem-RelocReqAck-IEs } } 

RAB-SetupItem-RelocReqAck-IEs RANAP-PROTOCOL-IES ::= ( 

{ ID id-RAB-SetupItem-RelocReqAck CRITICALITY reject TYPE RAB-SetupItem-RelocReqAck PRESENCE mandatory }, 

} 

RAB-SetupItem-RelocReqAck ::= SEQUENCE { 
rAB-ID RAB-ID, 

transportLayerAddress TransportLayerAddress OPTIONAL, 

iuTransportAssociation luTransportAssociation OPTIONAL, 

iE-Extensions ProtocolExtensionContainer ( { RAB-SetupItem-RelocReqAck-ExtlEs } } OPTIONAL, 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



145 



ETSI TS 125 413 V4.10.0 (2003-09) 



RAB-SetupItem-RelocReqAck-ExtlEs RANAP-PROTOCOL-EXTENSION ::= ( 

— Extension for Release 4 to enable RAB Quality of Service negotiation over lu — 

(ID id-Ass-RAB-Parameters CRITICALITY ignore EXTENSION Ass-RAB-Parameters 



PRESENCE optional } 



RAB-FailedList 



RAB-IE-ContainerList ( ( RAB-FailedltemlEs } } 



RAB-FailedltemlEs RANAP-PROTOCOL-IES 
{ ID id-RAB-Failedltem 



CRITICALITY ignore TYPE RAB-Failedltem 



PRESENCE mandatory }, 



RAB-Failedltem : := 
rAB-ID 
cause 
IE-Extensions 



SEQUENCE { 



RAB-ID, 
Cause, 

ProtocolExtensionContainer { ( RAB-Failedltem-ExtlEs } } 



OPTIONAL, 



RAB-Failedltem-ExtlEs RANAP-PROTOCOL-EXTENSION ::= { 



RelocationRequestAcknowledgeExtensions RANAP-PROTOCOL-EXTENSION ::= { 



************************************************************** 



Relocation Failure 



************************************************************** 



RelocationFailure ::= SEQUENCE { 

protocolIEs ProtocolIE-Container ( ( RelocationFailurelEs } }, 

protocolExtensions ProtocolExtensionContainer { { RelocationFailureExtensions } } 



OPTIONAL, 



RelocationFailurelEs RANAP-PROTOCOL-IES ::= { 

{ ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory } | 

{ ID Id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional 



RelocationFailureExtensions RANAP-PROTOCOL-EXTENSION ::= { 



************************************************************** 



— RELOCATION CANCEL ELEMENTARY PROCEDURE 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



146 



ETSI TS 125 413 V4.10.0 (2003-09) 



************************************************************** 

************************************************************** 



Relocation Cancel 
************************************************************** 



RelocationCancel ::= SEQUENCE { 

protocolIEs ProtocolIE-Container { ( RelocationCancellEs } }, 

protocolExtensions ProtocolExtensionContainer { { RelocationCancelExtensions } } 



OPTIONAL, 



RelocationCancellEs RANAP-PROTOCOL-IES ::= { 

( ID id-Cause CRITICALITY ignore TYPE Cause 



PRESENCE mandatory } , 



RelocationCancelExtensions RANAP-PROTOCOL-EXTENSION :;= { 
} 

************************************************************** 

— Relocation Cancel Acknowledge 

************************************************************** 



RelocationCancelAcknowledge : := SEQUENCE ( 

protocolIEs ProtocolIE-Container { { RelocationCancelAcknowledge lEs } } , 

protocolExtensions ProtocolExtensionContainer { { RelocationCancelAcknowledgeExtensions } } 



OPTIONAL, 



RelocationCancelAcknowledgelEs RANAP-PROTOCOL-IES ::= { 

( ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional 



RelocationCancelAcknowledgeExtensions RANAP-PROTOCOL-EXTENSION : := { 



************************************************************** 



SRNS CONTEXT TRANSFER OPEARATION 



************************************************************** 

************************************************************** 



— SRNS Context Request 



ETSI 



3GPP TS 25.413 version 4.10.0 Release 4 



147 



ETSI TS 125 413 V4.10.0 (2003-09) 



************************************************************** 



SRNS-ContextRequest ::= SEQUENCE { 

protocolIEs ProtocolIE-Container { ( SRNS-ContextRequestlEs } }, 

protocolExtensions ProtocolExtensionContainer { { SRNS-ContextRequestExtensions } } 



OPTIONAL, 



SRNS-ContextRequestlEs RANAP-PROTOCOL-IES ::= { 

{ ID id-RAB-DataForwardingList-SRNS-CtxReq CRITICALITY ignore TYPE RAB-DataForwardingList-SRNS-CtxReq PRESENCE mandatory 



RAB-DataForwardingList-SRNS-CtxReq 



RAB-IE-ContainerList ( ( RAB-DataForwardingltem-SRNS-CtxReq-IEs } } 



RAB-DataForwardingltem-SRNS-CtxReq-IEs RANAP-PROTOCOL-IES ::= ( 

{ ID id-RAB-DataForwardingltem-SRNS-CtxReq CRITICALITY reject TYPE RAB-DataForwardingltem-SRNS-CtxReq PRESENCE mandatory 



RAB-DataForwardingltem-SRNS-CtxReq ::= SEQUENCE { 
rAB-ID RAB-ID, 

iE-Extensions ProtocolExtensionContainer { { RAB-DataForwardingltem-SRNS-CtxReq-ExtlEs } } 



OPTIONAL, 



RAB-DataForwardingltem-SRNS-CtxReq-ExtlEs RANAP-PROTOCOL-EXTENSION ::= { 



SRNS-ContextRequestExtensions RANAP-PROTOCOL-EXTENSION ::= { 



************************************************************** 



SRNS Context Response 



************************************************************** 



SRNS-ContextResponse ::= SEQUENCE { 

protocolIEs ProtocolIE-Container { ( SRNS-ContextResponselEs } }, 

protocolExtensions ProtocolExtensionContainer { { SRNS-ContextResponseExtensions } } 



OPTIONAL, 



SRNS-ContextResponselEs RANAP-PROTOCOL-IES ::= { 

{ ID id-RAB-ContextList CRITICALITY ignore TYPE RAB-ContextList PRESENCE optional } 

{ ID Id-RAB-ContextFailedtoTransferList CRITICALITY ignore TYPE RAB-ContextFailedtoTransf erList PRESENCE optional } I 

{ ID Id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }, 

} 



RAB-ContextList 



RAB-IE-ContainerList { { RAB-ContextltemlEs } } 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 148 ETSI TS 125 413 V4.10.0 (2003-09) 

RAB-ContextltemlEs RANAP-PROTOCOL-IES ::= { 

{ ID id-RAB-Contextltem CRITICALITY ignore TYPE RAB-Contextltem PRESENCE mandatory }, 

} 

RAB-Contextltem ::= SEQUENCE ( 

rAB-ID RAB-ID, 

dl-GTP-PDU-SequenceNumber DL-GTP-PDU-SequenceNumber OPTIONAL, 

ul-GTP-PDU-SequenceNumber UL-GTP-PDU-SequenceNumber OPTIONAL, 

dl-N-PDU-SequenceNumber DL-N-PDU-SequenceNumber OPTIONAL, 

ul-N-PDU-SequenceNumber UL-N-PDU-SequenceNumber OPTIONAL, 

iE-Extensions ProtocolExtensionContainer ( ( RAB-Contextltem-ExtlEs } } OPTIONAL, 

} 

RAB-Contextltem-ExtlEs RANAP-PROTOCOL-EXTENSION ::= { 

} 

RAB-ContextFailedtoTransferList ::= RAB-IE-ContainerList ( ( RABs-ContextFailedtoTransf erItemlEs } } 

RABs-ContextFailedtoTransferltemlEs RANAP-PROTOCOL-IES ::= ( 

{ ID id-RAB-ContextFailedtoTransferltem CRITICALITY ignore TYPE RABs-ContextFailedtoTransf eritem PRESENCE mandatory }, 

} 

RABs-ContextFailedtoTransferltem: := SEQUENCE { 
rAB-ID RAB-ID, 

cause Cause, 

iE-Extensions ProtocolExtensionContainer ( ( RABs-ContextFailedtoTransf erItem-ExtlEs } } OPTIONAL, 



RABs-ContextFailedtoTransferltem-ExtlEs RANAP-PROTOCOL-EXTENSION ::= { 



SRNS-ContextResponseExtensions RANAP-PROTOCOL-EXTENSION ::= { 



************************************************************** 

— SECURITY MODE CONTROL ELEMENTARY PROCEDURE 

************************************************************** 

************************************************************** 



— Security Mode Command 



************************************************************** 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



149 



ETSI TS 125 413 V4.10.0 (2003-09) 



SecurityModeCommand ::= 
protocolIEs 
protocolExtensions 



SEQUENCE { 

ProtocolIE-Container ( ( SecurityModeCommandlEs } }, 

ProtocolExtensionContainer { { SecurityModeCommandExtensions } } 



OPTIONAL, 



SecurityModeCommandlEs RANAP-PROTOCOL-IES : := { 

{ ID id-IntegrityProtectionlnformation CRITICALITY reject TYPE IntegrityProtectionInf ormation PRESENCE mandatory } | 
{ ID id-Encryptionlnformation CRITICALITY ignore TYPE Encryptioninf ormation PRESENCE optional } 

{ ID id-KeyStatus CRITICALITY reject TYPE KeyStatus PRESENCE mandatory}. 



SecurityModeCommandExtensions RANAP-PROTOCOL-EXTENSION ::= { 



************************************************************** 



Security Mode Complete 



************************************************************** 



SecurityModeComplete ::= SEQUENCE { 

protocolIEs ProtocolIE-Container ( { SecurityModeCompletelEs } }, 

protocolExtensions ProtocolExtensionContainer { { SecurityModeCompleteExtensions } } 



OPTIONAL, 



SecurityModeCompletelEs RANAP-PROTOCOL-IES ::= { 

{ ID id-ChosenlntegrityProtectionAlgorithm CRITICALITY reject TYPE ChosenlntegrityProtectionAlgorithm PRESENCE mandatory 
{ ID Id-ChosenEncryptionAlgorithm CRITICALITY ignore TYPE ChosenEncryptionAlgorithm PRESENCE optional } 
{ ID Id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }, 



SecurityModeCompleteExtensions RANAP-PROTOCOL-EXTENSION ::= { 



************************************************************** 



— Security Mode Reject 



************************************************************** 



SecurityModeReject ::= SEQUENCE ( 

protocolIEs ProtocolIE-Container { ( SecurityModeRe jectlEs } }, 

protocolExtensions ProtocolExtensionContainer { { SecurityModeRe jectExtensions } 



OPTIONAL, 



SecurityModeRe jectlEs RANAP-PROTOCOL-IES 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



150 



ETSI TS 125 413 V4.10.0 (2003-09) 



{ ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory } | 

{ ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }, 



SecurityModeRejectExtensions RANAP-PROTOCOL-EXTENSION :;= { 

} 

************************************************************** 

— DATA VOLUME REPORT ELEMENTARY PROCEDURE 

************************************************************** 

************************************************************** 



— Data Volume Report Request 



************************************************************** 



DataVolumeReportRequest ::= SEQUENCE { 

protocolIEs ProtocolIE-Container { { DataVolumeReportRequestlEs } }, 

protocolExtensions ProtocolExtensionContainer { { DataVolumeReportRequestExtensions } } OPTIONAL, 

} 

DataVolumeReportRequestlEs RANAP-PROTOCOL-IES ::= { 

( ID Id-RAB-DataVolumeReportRequestList CRITICALITY ignore TYPE RAB-DataVolumeReportRequestList PRESENCE mandatory 



RAB-DataVolumeReport Request List 



RAB-IE-ContainerList { { RAB-DataVolumeReportRequestltemlEs } } 



RAB-DataVolumeReportRequestltemlEs RANAP-PROTOCOL-IES ::= { 

{ ID Id-RAB-DataVolumeReportRequestltem CRITICALITY reject TYPE RAB-DataVolumeReportRequestltem PRESENCE mandatory 

} 

RAB-DataVolumeReportRequestltem ::= SEQUENCE { 
rAB-ID RAB-ID, 

IE-Extensions ProtocolExtensionContainer ( { RAB-DataVolumeReportRequestltem-ExtlEs } } OPTIONAL, 



RAB-DataVolumeReportRequestltem-ExtlEs RANAP-PROTOCOL-EXTENSION ::= { 

} 

DataVolumeReportRequestExtensions RANAP-PROTOCOL-EXTENSION ::= { 

} 

************************************************************** 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



151 



ETSI TS 125 413 V4.10.0 (2003-09) 



— Data Volume Report 



************************************************************** 



DataVolumeReport ::= SEQUENCE { 

protocolIEs ProtocolIE-Container { { DataVolumeReportlEs } }, 

protocolExtensions ProtocolExtensionContainer { { DataVolumeReportExtensions } } 



OPTIONAL, 



DataVolumeReportlEs RANAP-PROTOCOL-IES 
( ID Id-RAB-DataVolumeReportList 
{ ID Id-RAB-FailedtoReportList 
{ ID Id-CriticalityDiagnostics 



{ 



CRITICALITY ignore TYPE RAB-DataVolumeReportList 
CRITICALITY ignore TYPE RAB-FailedtoReportList 
CRITICALITY ignore TYPE CriticalityDiagnostics 



PRESENCE optional 
PRESENCE optional } 
PRESENCE optional }, 



DataVolumeReportExtensions RANAP-PROTOCOL-EXTENSION ::= { 



RAB-FailedtoReportList 



RAB-IE-ContainerLlst ( ( RABs-f ailed-to-reportltemlEs } } 



RABs-failed-to-reportltemlEs RANAP-PROTOCOL-IES ::= { 

{ ID id-RAB-FailedtoReportltem CRITICALITY ignore TYPE RABs-f ailed-to-reportltem PRESENCE mandatory 



RABs-f ailed-to-reportltem: := 
rAB-ID 
cause 
IE-Extensions 



SEQUENCE { 
RAB-ID, 
Cause, 

ProtocolExtensionContainer { ( RABs-f ailed-to-reportltem-ExtlEs } } 



OPTIONAL, 



RABs-f ailed-to-report I tem-ExtlEs RANAP-PROTOCOL-EXTENSION 



************************************************************** 



RESET ELEMENTARY PROCEDURE 



************************************************************** 

************************************************************** 



— Reset 



************************************************************** 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



152 



ETSI TS 125 413 V4.10.0 (2003-09) 



Reset : := SEQUENCE { 

protocolIEs ProtocolIE-Container ( (ResetlEs} }, 

protocolExtensions ProtocolExtensionContainer { { ResetExtensions } } 



OPTIONAL, 



} 



ResetlEs RANAP-PROTOCOL-IES ::= 
{ ID id-Cause 

{ ID id-CN-Domainlndicator 
{ ID id-GlobalRNC-ID 



CRITICALITY ignore TYPE Cause PRESENCE mandatory } | 

CRITICALITY reject TYPE CN-Domainlndicator PRESENCE mandatory 

CRITICALITY ignore TYPE GlobalRNC-ID PRESENCE optional}, 



ResetExtensions RANAP-PROTOCOL-EXTENSION ::= { 
— Extension for Release 4 — 

{ ID id-GlobalCN-ID CRITICALITY ignore 



EXTENSION GlobalCN-ID 



PRESENCE optional}. 



************************************************************** 



Reset Acknowledge 



************************************************************** 



ResetAcknowledge ::= SEQUENCE { 

protocolIEs ProtocolIE-Container { { ResetAcknowledgelEs } }, 

protocolExtensions ProtocolExtensionContainer { { ResetAcknowledgeExtensions } } 



OPTIONAL, 



ResetAcknowledgelEs RANAP-PROTOCOL-IES ::= { 

{ ID id-CN-Domainlndicator CRITICALITY reject TYPE CN-Domainlndicator PRESENCE mandatory 

{ ID Id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional 

{ ID id-GlobalRNC-ID CRITICALITY ignore TYPE GlobalRNC-ID PRESENCE optional}. 



ResetAcknowledgeExtensions RANAP-PROTOCOL-EXTENSION ::= { 
— Extension for Release 4 — 

{ ID id-GlobalCN-ID CRITICALITY ignore EXTENSION GlobalCN-ID 



PRESENCE optional}. 



************************************************************** 



RESET RESOURCE ELEMENTARY PROCEDURE 



************************************************************** 



************************************************************** 



— Reset Resource 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



153 



ETSI TS 125 413 V4.10.0 (2003-09) 



************************************************************** 



ResetResource ::= SEQUENCE { 

protocolIEs ProtocolIE-Container ( { ResetResourcelEs } }, 

protocolExtensions ProtocolExtensionContainer { { ResetResourceExtensions } } 



OPTIONAL, 



ResetResourcelEs RANAP-PROTOCOL-IES ::= { 

{ ID id-CN-Domainlndicator CRITICALITY reject TYPE CN-Domainlndicator PRESENCE mandatory 

{ ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory } | 

{ ID id-IuSigConldList CRITICALITY ignore TYPE ResetResourceList PRESENCE mandatory 

{ ID id-GlobalRNC-ID CRITICALITY ignore TYPE GlobalRNC-ID PRESENCE optional}, 



ResetResourceList ::= luSigConld-IE-ContainerList ( ( ResetResourceltemlEs } } 



ResetResourceltemlEs RANAP-PROTOCOL-IES ::= { 

( ID id-IuSigConldltem CRITICALITY reject TYPE ResetResourceltem 



PRESENCE mandatory 



} 



ResetResourceltem ::= SEQUENCE { 

iuSigConId I uSignallingConnect ion Identifier, 

iE-Extensions ProtocolExtensionContainer { { ResetResourceltem-ExtlEs } } 



OPTIONAL, 



} 

ResetResourceltem-ExtlEs RANAP-PROTOCOL-EXTENSION ::= { 

} 



ResetResourceExtensions RANAP-PROTOCOL-EXTENSION ::= { 
— Extension for Release 4 — 

{ ID id-GlobalCN-ID CRITICALITY ignore EXTENSION GlobalCN-ID 



PRESENCE optional}, 



************************************************************** 



— Reset Resource Acknowledge 



************************************************************** 



ResetResourceAcknowledge : := SEQUENCE ( 

protocolIEs ProtocolIE-Container ( { ResetResourceAcknowledgelEs } }, 

protocolExtensions ProtocolExtensionContainer { { ResetResourceAcknowledgeExtensions } 



OPTIONAL, 



ResetResourceAcknowledgelEs RANAP-PROTOCOL-IES ;;= { 

{ ID id-CN-Domainlndicator CRITICALITY reject TYPE CN-Domainlndicator 

{ ID id-IuSigConldList CRITICALITY ignore TYPE ResetResourceAckList 



PRESENCE mandatory 
PRESENCE mandatory 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



154 



ETSI TS 125 413 V4.10.0 (2003-09) 



{ ID id-GlobalRNC-ID 

{ ID id-CriticalityDiagnostics 



CRITICALITY ignore TYPE GlobalRNC-ID PRESENCE optional } I 

CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }, 



ResetResourceAckList 



luSigConld-IE-ContainerList { { ResetResourceAckltemlEs } } 



ResetResourceAckltemlEs RANAP-PROTOCOL-IES ::= ( 

{ ID id-IuSigConldltem CRITICALITY reject TYPE ResetResourceAckltem 



PRESENCE mandatory }, 



ResetResourceAckltem 
iuSigConId 
IE-Extensions 



SEQUENCE { 

I uSignallingConnect ion Identifier, 

ProtocolExtensionContainer { { ResetResourceAckltem-ExtlEs } } 



OPTIONAL, 



ResetResourceAckltem-ExtlEs RANAP-PROTOCOL-EXTENSION ;;= { 
} 



ResetResourceAcknowledgeExtensions RANAP-PROTOCOL-EXTENSION ::= { 
— Extension for Release 4 — 

{ ID id-GlobalCN-ID CRITICALITY ignore EXTENSION GlobalCN-ID 



PRESENCE optional}, 



************************************************************** 

— RAB RELEASE REQUEST ELEMENTARY PROCEDURE 

************************************************************** 

************************************************************** 



— RAB Release Request 



************************************************************** 



RAB-ReleaseRequest ::= SEQUENCE { 

protocolIEs ProtocolIE-Container { ( RAB-ReleaseRequestlEs } }, 

protocolExtensions ProtocolExtensionContainer { { RAB-ReleaseRequestExtensions } } 



OPTIONAL, 



RAB-ReleaseRequestlEs RANAP-PROTOCOL-IES ::= { 

( ID Id-RAB-ReleaseList CRITICALITY ignore TYPE RAB-ReleaseList 



PRESENCE mandatory }, 



RAB-ReleaseList 



RAB-IE-ContainerList { { RAB-ReleaseltemlEs } } 



RAB-ReleaseltemlEs RANAP-PROTOCOL-IES ::= { 

{ ID id-RAB-Releaseltem CRITICALITY ignore TYPE RAB-Releaseltem 



PRESENCE mandatory 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



155 



ETSI TS 125 413 V4.10.0 (2003-09) 



RAB-Releaseltem ::= SEQUENCE { 

rAB-ID RAB-ID, 

cause Cause, 

iE-Extensions ProtocolExtensionContainer { { RAB-Releaseltem-ExtlEs } } 



OPTIONAL, 



RAB-Releaseltem-ExtlEs RANAP-PROTOCOL-EXTENSION ::= { 



RAB-ReleaseRequestExtensions RANAP-PROTOCOL-EXTENSION ::= { 



************************************************************** 

— lu RELEASE REQUEST ELEMENTARY PROCEDURE 

************************************************************** 

************************************************************** 



— lu Release Request 



************************************************************** 



lu-ReleaseRequest ::= SEQUENCE ( 

protocolIEs ProtocolIE-Container ( ( lu-ReleaseRequestlEs } }, 

protocolExtensions ProtocolExtensionContainer { { lu-ReleaseRequestExtensions } } 



OPTIONAL, 



lu-ReleaseRequestlEs RANAP-PROTOCOL-IES ::= { 

( ID id-Cause CRITICALITY ignore TYPE Cause 



PRESENCE mandatory } , 



lu-ReleaseRequestExtensions RANAP-PROTOCOL-EXTENSION ::= { 



************************************************************** 



RELOCATION DETECT ELEMENTARY PROCEDURE 



************************************************************** 

************************************************************** 



Relocation Detect 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 156 ETSI TS 125 413 V4.10.0 (2003-09) 

************************************************************** 

RelocationDetect ::= SEQUENCE { 

protocolIEs ProtocolIE-Container { { RelocationDetectlEs } }, 

protocolExtensions ProtocolExtensionContainer { { RelocationDetectExtensions } } OPTIONAL, 

} 

RelocationDetectlEs RANAP-PROTOCOL-IES ::= { 

} 

RelocationDetectExtensions RANAP-PROTOCOL-EXTENSION :;= { 

} 

************************************************************** 

— RELOCATION COMPLETE ELEMENTARY PROCEDURE 

************************************************************** 

************************************************************** 

— Relocation Complete 

************************************************************** 

RelocationComplete ::= SEQUENCE ( 

protocolIEs ProtocolIE-Container { { RelocationCompletelEs } }, 

protocolExtensions ProtocolExtensionContainer { { RelocationCompleteExtensions } } OPTIONAL, 

} 

RelocationCompletelEs RANAP-PROTOCOL-IES : := { 

} 

RelocationCompleteExtensions RANAP-PROTOCOL-EXTENSION : := { 

} 

************************************************************** 

— PAGING ELEMENTARY PROCEDURE 

************************************************************** 

************************************************************** 

— Paging 

************************************************************** 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



157 



ETSI TS 125 413 V4.10.0 (2003-09) 



Paging ::= SEQUENCE { 

protocolIEs ProtocolIE-Container { {PaginglEs} }, 

protocolExtensions ProtocolExtensionContainer { { PagingExtensions } } 



OPTIONAL, 



} 



PaginglEs RANAP-PROTOCOL-IES ::= { 

{ ID id-CN-Domainlndicator 

{ ID id-PermanentNAS-UE-ID 

{ ID id-TemporaryUE-ID 

{ ID id-PagingArealD 

{ ID id-PagingCause 

{ ID id-NonSearchinglndication 

{ ID id-DRX-CycleLengthCoef ficient 



CRITICALITY ignore TYPE CN-Domainlndicator 
CRITICALITY ignore TYPE PermanentNAS-UE-ID 
CRITICALITY ignore TYPE TemporaryUE-ID 
CRITICALITY ignore TYPE PagingArealD 
CRITICALITY ignore TYPE PagingCause 



PRESENCE mandatory } 
PRESENCE mandatory } 
PRESENCE optional } I 
PRESENCE optional } I 
PRESENCE optional } I 



CRITICALITY ignore TYPE NonSearchinglndication PRESENCE optional } 

CRITICALITY ignore TYPE DRX-CycleLengthCoef ficient PRESENCE optional 



PagingExtensions RANAP-PROTOCOL-EXTENSION 



************************************************************** 



— COMMON ID ELEMENTARY PROCEDURE 



************************************************************** 

************************************************************** 



Common ID 



************************************************************** 



CommonID ::= SEQUENCE { 

protocolIEs ProtocolIE-Container ( { CommonlD-IEs } }, 

protocolExtensions ProtocolExtensionContainer { { CommonlDExtensions } } 



OPTIONAL, 



CommonlD-IEs RANAP-PROTOCOL-IES 
{ ID id-PermanentNAS-UE-ID 



CRITICALITY ignore TYPE PermanentNAS-UE-ID 



PRESENCE mandatory }, 



CommonlDExtensions RANAP-PROTOCOL-EXTENSION ;;= { 



************************************************************** 



— CN INVOKE TRACE ELEMENTARY PROCEDURE 



************************************************************** 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



158 



ETSI TS 125 413 V4.10.0 (2003-09) 



************************************************************** 



CN Invoke Trace 



************************************************************** 



CN-InvokeTrace ::= SEQUENCE { 

protocolIEs ProtocolIE-Container { { CN-InvokeTracelEs } }, 

protocolExtensions ProtocolExtensionContainer { { CN-InvokeTraceExtensions } } 



OPTIONAL, 



} 



CN-InvokeTracelEs RANAP-PROTOCOL-IES ::= { 

{ ID id-TraceType CRITICALITY ignore TYPE TraceType 

{ ID id-TraceReference CRITICALITY ignore TYPE TraceRef erence 

{ ID id-TriggerlD CRITICALITY ignore TYPE TriggerlD 

{ ID id-UE-ID CRITICALITY ignore TYPE UE-ID 

{ ID id-OMC-ID CRITICALITY ignore TYPE OMC-ID 



PRESENCE mandatory } | 
PRESENCE mandatory 

PRESENCE optional } I 
PRESENCE optional } I 
PRESENCE optional }, 



CN-InvokeTraceExtensions RANAP-PROTOCOL-EXTENSION 



************************************************************** 



CN DEACTIVATE TRACE ELEMENTARY PROCEDURE 



************************************************************** 

************************************************************** 



— CN Deactivate Trace 



************************************************************** 



CN-DeactivateTrace ::= SEQUENCE ( 

protocolIEs ProtocolIE-Container ( { CN-DeactivateTracelEs } }, 

protocolExtensions ProtocolExtensionContainer { ( CN-DeactivateTraceExtensions } } 



OPTIONAL, 



CN-DeactivateTracelEs RANAP-PROTOCOL-IES ::= { 

{ ID id-TraceReference CRITICALITY ignore TYPE TraceRef erence 

{ ID id-TriggerlD CRITICALITY ignore TYPE TriggerlD 



PRESENCE mandatory } | 
PRESENCE optional } , 



CN-DeactivateTraceExtensions RANAP-PROTOCOL-EXTENSION 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 159 ETSI TS 125 413 V4.10.0 (2003-09) 



************************************************************** 

— LOCATION REPORTING CONTROL ELEMENTARY PROCEDURE 

************************************************************** 

************************************************************** 

— Location Reporting Control 

************************************************************** 

LocationReportingControl ::= SEQUENCE ( 

protocolIEs ProtocolIE-Container ( { LocationReportingControlIEs } }, 

protocolExtensions ProtocolExtensionContainer { { LocationReportingControlExtensions } } OPTIONAL, 

} 

LocationReportingControlIEs RANAP-PROTOCOL-IES ::= { 

( ID Id-RequestType CRITICALITY ignore TYPE RequestType PRESENCE mandatory }, 

} 

LocationReportingControlExtensions RANAP-PROTOCOL-EXTENSION ::= { 

— Extension for Release 4 to enhance the location request over lu — 

{ ID id-VerticalAccuracyCode CRITICALITY ignore EXTENSION VerticalAccuracyCode PRESENCE optional } I 

— Extension for Release 4 to enhance the location request over lu — 

{ ID Id-ResponseTime CRITICALITY ignore EXTENSION ResponseTime PRESENCE optional } 

— Extension for Release 4 to enhance the location request over lu — 

( ID id-PositioningPriority CRITICALITY ignore EXTENSION PositioningPriority PRESENCE optional } I 

— Extension for Release 4 to enhance the location request over lu — 

( ID Id-ClientType CRITICALITY ignore EXTENSION ClientType PRESENCE optional}, 

} 

************************************************************** 

— LOCATION REPORT ELEMENTARY PROCEDURE 

************************************************************** 

************************************************************** 

— Location Report 

************************************************************** 

LocationReport ::= SEQUENCE { 

protocolIEs ProtocolIE-Container { ( LocationReportlEs } }, 

protocolExtensions ProtocolExtensionContainer ( { LocationReport Ext ens ions } } OPTIONAL, 



LocationReportlEs RANAP-PROTOCOL-IES 



ETSi 



3GPP TS 25.413 version 4.10.0 Release 4 



160 



ETSI TS 125 413 V4.10.0 (2003-09) 



{ ID id-Arealdentity 

{ ID id-Cause 

{ ID id-RequestType 



CRITICALITY ignore TYPE Arealdentity 
CRITICALITY ignore TYPE Cause 

CRITICALITY ignore TYPE RequestType 



PRESENCE optional } I 
PRESENCE optional } I 

PRESENCE optional } , 



} 



LocationReportExtensions RANAP-PROTOCOL-EXTENSION ::= ( 

— Extension for Release 4 to enable report of Last Known Service Area with its Age over lu — 

{ ID Id-LastKnownServiceArea CRITICALITY ignore EXTENSION LastKnownServiceArea PRESENCE optional}, 



************************************************************** 



— INITIAL UE MESSAGE ELEMENTARY PROCEDURE 

************************************************************** 



************************************************************** 



Initial UE Message 



************************************************************** 



InitialUE -Message ::= SEQUENCE { 

protocolIEs ProtocolIE-Container { ( InitialUE-MessagelEs } }, 
protocolExtensions ProtocolExtensionContainer { { InitialUE -MessageExtensions } } 



OPTIONAL, 



InitialUE-MessagelEs RANAP-PROTOCOL-IES ::= { 

{ ID id-CN-Domainlndicator CRITICALITY ignore TYPE CN-Domainlndicator PRESENCE mandatory } 

{ ID id-LAI CRITICALITY ignore TYPE LAI PRESENCE mandatory } 

{ ID id-RAC CRITICALITY ignore TYPE RAO PRESENCE conditional 

— This IE shall be present if the CM Domain Indicator IE is set to "PS domain" — 

{ ID id-SAI CRITICALITY ignore TYPE SAI PRESENCE mandatory } 

{ ID id-NAS-PDU CRITICALITY ignore TYPE NAS-PDU PRESENCE mandatory } | 

{ ID id-IuSigConId CRITICALITY ignore TYPE luSignallingConnectionldentif ier PRESENCE mandatory 

{ ID id-GlobalRNC-ID CRITICALITY ignore TYPE GlobalRNC-ID PRESENCE mandatory }, 



InitialUE-MessageExtensions RANAP-PROTOCOL-EXTENSION ::= { 



************************************************************** 



— DIRECT TRANSFER ELEMENTARY PROCEDURE 

************************************************************** 



************************************************************** 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



161 



ETSI TS 125 413 V4.10.0 (2003-09) 



— Direct Transfer 



************************************************************** 



DirectTransfer ::= SEQUENCE { 

protocolIEs ProtocolIE-Container { { DirectTransf erIEs } }, 

protocolExtensions ProtocolExtensionContainer { { DirectTransf erExtensions } } 



OPTIONAL, 



DirectTransferlEs RANAP-PROTOCOL-IES ::= { 

( ID id-NAS-PDU CRITICALITY ignore TYPE NAS-PDU 

{ ID id-LAI CRITICALITY ignore TYPE LAI 

{ ID id-RAC CRITICALITY ignore TYPE RAC 

{ ID id-SAI CRITICALITY ignore TYPE SAI 

{ ID id-SAPI CRITICALITY ignore TYPE SAPI 



PRESENCE mandatory } | 
PRESENCE optional } 
PRESENCE optional } 
PRESENCE optional } 

PRESENCE optional }, 



DirectTransf erExtensions RANAP-PROTOCOL-EXTENSION 



************************************************************** 



— OVERLOAD CONTROL ELEMENTARY PROCEDURE 



************************************************************** 
************************************************************** 



— Overload 



************************************************************** 



Overload ::= SEQUENCE ( 

protocolIEs ProtocolIE-Container ( { OverloadlEs } }, 

protocolExtensions ProtocolExtensionContainer { { OverloadExtensions } } 



OPTIONAL, 



OverloadlEs RANAP-PROTOCOL-IES 
{ ID id-NumberOfSteps 
{ ID id-GlobalRNC-ID 



CRITICALITY ignore TYPE NumberOf Steps 
CRITICALITY ignore TYPE GlobalRNC-ID 



PRESENCE optional } I 
PRESENCE optional } , 



OverloadExtensions RANAP-PROTOCOL-EXTENSION ::= { 

— Extension for Release 99 to enable the indication to the RNC which CN domain is suffering the signalling traffic overload 
{ ID id-CN-Domainlndicator CRITICALITY ignore EXTENSION CN-Domainlndicator PRESENCE optional } , 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



162 



ETSI TS 125 413 V4.10.0 (2003-09) 



************************************************************** 



— ERROR INDICATION ELEMENTARY PROCEDURE 

************************************************************** 



************************************************************** 



— Error Indication 



************************************************************** 



Errorlndication ::= SEQUENCE ( 

protocolIEs ProtocolIE-Container ( { ErrorlndicationlEs } }, 

protocolExtensions ProtocolExtensionContainer { { ErrorlndicationExtensions } } 



OPTIONAL, 



ErrorlndicationlEs RANAP-PROTOCOL-IES ::= { 

{ ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE optional } I 

{ ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional 

{ ID id-CN-Domainlndicator CRITICALITY ignore TYPE CN-Domainlndicator PRESENCE optional 

{ ID id-GlobalRNC-ID CRITICALITY ignore TYPE GlobalRNC-ID PRESENCE optional}, 



ErrorlndicationExtensions RANAP-PROTOCOL-EXTENSION ::= 
— Extension for Release 4 — 

{ ID id-GlobalCN-ID CRITICALITY ignore 



EXTENSION GlobalCN-ID 



PRESENCE optional}, 



************************************************************** 



— SRNS DATA FORWARD ELEMENTARY PROCEDURE 

************************************************************** 



************************************************************** 



— SRNS Data Forward Command 



************************************************************** 



SRNS-DataForwardCommand ::= SEQUENCE ( 

protocolIEs ProtocolIE-Container { ( SRNS-DataForwardCommandlEs } }, 

protocolExtensions ProtocolExtensionContainer { { SRNS-DataForwardCommandExtensions } } 



OPTIONAL, 



SRNS-DataForwardCommandlEs RANAP-PROTOCOL-IES ::= { 

{ ID Id-RAB-DataForwardingLlst CRITICALITY ignore TYPE RAB-DataForwardingLlst 



PRESENCE optional }, 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



163 



ETSI TS 125 413 V4.10.0 (2003-09) 



SRNS-DataForwardCommandExtensions RANAP-PROTOCOL-EXTENSION ::= { 

} 

************************************************************** 

— FORWARD SRNS CONTEXT ELEMENTARY PROCEDURE 

************************************************************** 

************************************************************** 

— Forward SRNS Context 

************************************************************** 



ForwardSRNS-Context ::= SEQUENCE { 

protocolIEs ProtocolIE-Container ( ( ForwardSRNS-ContextlEs } }, 

protocolExtensions ProtocolExtensionContainer { { ForwardSRNS-ContextExtensions } } 

} 

ForwardSRNS-ContextlEs RANAP-PROTOCOL-IES ::= { 

{ ID id-RAB-ContextList CRITICALITY ignore TYPE RAB-ContextList 



OPTIONAL, 



PRESENCE mandatory }, 



ForwardSRNS-ContextExtensions RANAP-PROTOCOL-EXTENSION ::= { 



************************************************************** 



— RAB ASSIGNMENT ELEMENTARY PROCEDURE 



************************************************************** 
************************************************************** 



— RAB Assignment Request 



************************************************************** 



RAB-AssignmentRequest : := SEQUENCE ( 

protocolIEs ProtocolIE-Container ( { RAB-AssignmentRequestlEs } }, 

protocolExtensions ProtocolExtensionContainer { { RAB-AssignmentRequestExtensions } } 



OPTIONAL, 



RAB-AssignmentRequestlEs RANAP-PROTOCOL-IES ::= { 

{ ID Id-RAB-SetupOrModifyList CRITICALITY ignore TYPE RAB-SetupOrModif yList 

{ ID Id-RAB-ReleaseList CRITICALITY ignore TYPE RAB-ReleaseList 



PRESENCE optional 
PRESENCE optional 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



164 



ETSI TS 125 413 V4.10.0 (2003-09) 



RAB-SetupOrModifyList 



: := RAB-IE-ContainerPairList { { RAB-SetupOrModif yItem-IEs } } 



RAB-SetupOrModifyltem-IEs RANAP-PROTOCOL-IES-PAIR ::= { 

{ ID id-RAB-SetupOrModifyltem FIRST CRITICALITY reject FIRST TYPE RAB-SetupOrModif yItemFirst 

SECOND CRITICALITY ignore SECOND TYPE RAB-SetupOrModif yItemSecond 

PRESENCE mandatory } , 



RAB-SetupOrModifyltemFirst ::= SEQUENCE { 
rAB-ID RAB-ID, 

nAS-Synchroni sat ion Indicator NAS -Synchronisation Indicator 
rAB-Parameters RAB-Parameters 

userPlaneInf ormation 
transportLayer Information 
service -Handover 



OPTIONAL, 
OPTIONAL, 
UserPlanelnformation OPTIONAL, 

TransportLayer Information OPTIONAL, 
Service-Handover OPTIONAL, 



iE-Extensions 



ProtocolExtensionContainer ( { RAB-SetupOrModif yItemFirst-ExtlEs } } 



OPTIONAL, 



TransportLayerInf ormation : 
transportLayerAddress 
iuTransportAssociation 
iE-Extensions 



SEQUENCE ( 

TransportLayerAddress, 

IuTransportAssociation, 

ProtocolExtensionContainer { {TransportLayerlnformation-ExtlEs } } 



OPTIONAL, 



} 

TransportLayer Information-ExtlEs RANAP-PROTOCOL-EXTENSION 



RAB-SetupOrModifyltemFirst-ExtlEs RANAP-PROTOCOL-EXTENSION ::= { 



RAB-SetupOrModifyltemSecond 



SEQUENCE { 



pDP-Type Information 

dataVolumeReportinglndication 

dl-GTP-PDU-SequenceNumber 

ul-GTP-PDU-SequenceNumber 

dl-N-PDU-SequenceNumber 

ul-N-PDU-SequenceNumber 

iE-Extensions 



PDP-Typelnformation OPTIONAL, 

DataVolumeReportinglndication OPTIONAL, 

DL-GTP-PDU-SequenceNumber OPTIONAL, 

UL-GTP-PDU-SequenceNumber OPTIONAL, 

DL-N-PDU-SequenceNumber OPTIONAL, 

UL-N-PDU-SequenceNumber OPTIONAL, 
ProtocolExtensionContainer { { RAB-SetupOrModif yItemSecond-ExtlEs } } 



OPTIONAL, 



RAB-SetupOrModifyltemSecond-ExtlEs RANAP-PROTOCOL-EXTENSION ;;= { 

— Extension for Release 4 to enable RAB Quality of Service negotiation over lu — 

{ ID id-Alt-RAB-Parameters CRITICALITY ignore EXTENSION Alt-RAB-Parameters 



PRESENCE optional 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 

RAB-AssignmentRequestExtensions RANAP-PROTOCOL-EXTENSION ::= { 
} 

************************************************************** 



165 



ETSI TS 125 413 V4.10.0 (2003-09) 



RAB Assignment Response 



************************************************************** 



RAB-AssignmentResponse : := SEQUENCE { 

protocolIEs ProtocolIE-Container ( { RAB-AssignmentResponselEs } }, 

protocolExtensions ProtocolExtensionContainer { { RAB-AssignmentResponseExtensions } } 



OPTIONAL, 



RAB-AssignmentResponselEs RANAP-PROTOCOL-IES ::= { 

{ ID id-RAB-SetupOrModifiedList CRITICALITY ignore TYPE RAB-SetupOrModif iedList 

{ ID id-RAB-ReleasedList CRITICALITY ignore TYPE RAB-ReleasedList 



PRESENCE optional 
PRESENCE optional } 



{ ID Id-RAB-QueuedList 

{ ID Id-RAB-FailedList 

{ ID id-RAB-ReleaseFailedList 

{ ID Id-CriticalityDiagnostics 



CRITICALITY ignore TYPE RAB-QueuedList PRESENCE optional } I 

CRITICALITY ignore TYPE RAB-FailedList PRESENCE optional } | 

CRITICALITY ignore TYPE RAB-ReleaseFailedList PRESENCE optional 
CRITICALITY ignore TYPE CrlticalityDlagnostics PRESENCE optional }, 



RAB-SetupOrModif iedList 



RAB-IE-ContainerLlst { { RAB-SetupOrModif iedltemlEs } } 



RAB-SetupOrModifiedltemlEs RANAP-PROTOCOL-IES ::= ( 

( ID Id-RAB-SetupOrModifiedltem CRITICALITY ignore TYPE RAB-SetupOrModif iedltem 



PRESENCE mandatory }, 



RAB-SetupOrModif iedltem : := 
rAB-ID 

transportLayerAddress 
luTransportAssociation 
dl-dataVolumes 
IE-Extensions 



SEQUENCE { 
RAB-ID, 

TransportLayerAddress OPTIONAL, 
luTransportAssociation OPTIONAL, 
DataVolumeLlst OPTIONAL, 
ProtocolExtensionContainer ( ( RAB-SetupOrModif iedltem-ExtlEs } } 



OPTIONAL, 



RAB-SetupOrModifiedltem-ExtlEs RANAP-PROTOCOL-EXTENSION ::= { 

— Extension for Release 4 to enable RAB Quality of Service negotiation over lu — 

( ID id-Ass-RAB-Parameters CRITICALITY ignore EXTENSION Ass-RAB-Parameters 



PRESENCE optional 



RAB-ReleasedList 



RAB-IE-ContainerList { {RAB-ReleasedltemlEs } } 



RAB-ReleasedltemlEs RANAP-PROTOCOL-IES ::= { 

{ ID id-RAB-Releasedltem CRITICALITY ignore TYPE RAB-Releasedltem 



PRESENCE mandatory }, 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



} 



166 



RAB-Releasedltem ::= SEQUENCE { 
rAB-ID 

dl-dataVolumes 
dL-GTP-PDU-SequenceNumber 
uL-GTP-PDU-SequenceNumber 
iE-Ext ens ions 



RAB-ID, 

DataVolumeList OPTIONAL, 

DL-GTP-PDU-SequenceNumber OPTIONAL, 

UL-GTP-PDU-SequenceNumber OPTIONAL, 

ProtocolExtensionContainer ( (RAB-Releasedltem-ExtlEs } } 



ETSI TS 125 413 V4.10.0 (2003-09) 



OPTIONAL, 



RAB-Releasedltem-ExtlEs RANAP-PROTOCOL-EXTENSION ::= { 
} 

DataVolumeList ::= SEQUENCE (SIZE ( 1 . . maxNrOfVol) ) OF 
SEQUENCE { 

dl-Unsuccessf ullyTransmittedDataVolume Unsuccessf ullyTransmittedDataVolume, 

dataVolumeReference DataVolumeReference OPTIONAL, 

iE-Extensions ProtocolExtensionContainer { (DataVolumeList-ExtlEs } } OPTIONAL, 

} 

DataVolumeList-ExtlEs RANAP-PROTOCOL-EXTENSION ::= { 

} 

RAB-QueuedList ;:= RAB-IE-ContainerList { { RAB-QueuedltemlEs } } 



RAB-QueuedltemlEs RANAP-PROTOCOL-IES ::= ( 

( ID id-RAB-Queuedltem CRITICALITY ignore TYPE RAB-Queuedltem 



PRESENCE mandatory 



RAB-Queuedltem ::= SEQUENCE { 

rAB-ID RAB-ID, 

iE-Extensions ProtocolExtensionContainer { { RAB-Queuedltem-ExtlEs } } 



OPTIONAL, 



RAB-Queuedltem-ExtlEs RANAP-PROTOCOL-EXTENSION ::= { 

} 

RAB-ReleaseFailedList : := RAB-FailedList 

RAB-AssignmentResponseExtensions RANAP-PROTOCOL-EXTENSION ::= { 

} 

************************************************************** 

— PRIVATE MESSAGE 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 167 ETSI TS 125 413 V4.10.0 (2003-09) 

************************************************************** 

PrivateMessage ::= SEQUENCE { 

privatelEs PrivatelE-Container { { PrivateMessage-IEs } }, 

} 

PrivateMessage-IEs RANAP-PRIVATE-IES ::= { 

} 

************************************************************** 

— RANAP RELOCATION INFORMATION ELEMENTARY PROCEDURE 

************************************************************** 

RANAP-Relocationlnformation ::= SEQUENCE { 

protocolIEs ProtocolIE-Container ( (RANAP-RelocationlnformationlEs } }, 

protocolExtensions ProtocolExtensionContainer { { RANAP-RelocationInf ormationExtensions } } OPTIONAL, 

} 

RANAP-RelocationlnformationlEs RANAP-PROTOCOL-IES ::= { 
{ ID id-DirectTransferlnformationList-RANAP-RelocInf 

CRITICALITY ignore TYPE DirectTransf erinf ormationList-RANAP-RelocInf 

PRESENCE optional } I 
{ ID id-RAB-ContextList-RANAP-RelocInf CRITICALITY ignore TYPE RAB-ContextList-RANAP-RelocInf PRESENCE optional }, 

} 

DirectTransf erInformationList-RANAP-RelocInf ::= DirectTransf er-IE-ContainerList { { DirectTransf erInf ormationltemlEs-RANAP-RelocInf } } 

DirectTransf erInformationltemlEs-RANAP-RelocInf RANAP-PROTOCOL-IES ::= ( 
{ ID Id-DirectTransferlnformationltem-RANAP-RelocInf 

CRITICALITY ignore TYPE DirectTransf erInformationltem-RANAP-RelocInf 

PRESENCE mandatory } , 

} 

DirectTransferlnformationltem-RANAP-RelocInf : := SEQUENCE { 
nAS-PDU NAS-PDU, 

SAP I SAP I , 

cN-Domain Indicator CN-Domain Indicator, 

iE-Extensions ProtocolExtensionContainer ( ( RANAP-DirectTransf erInf ormationltem-ExtlEs-RANAP-RelocInf } } OPTIONAL, 

} 

RANAP-DirectTransferlnformationltem-ExtlEs-RANAP-RelocInf RANAP-PROTOCOL-EXTENSION ::= { 

} 

RAB-ContextList-RANAP-RelocInf ::= RAB-IE-ContainerList { { RAB-ContextltemlEs-RANAP-RelocInf } } 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 168 ETSI TS 125 413 V4.10.0 (2003-09) 

RAB-ContextltemlEs-RANAP-RelocInf RANAP-PROTOCOL-IES ::= { 

{ ID id-RAB-Contextltem-RANAP-RelocInf CRITICALITY ignore TYPE RAB-Contextltem-RANAP-RelocInf PRESENCE mandatory }, 

} 

RAB-Contextltem-RANAP-RelocInf ::= SEQUENCE { 
rAB-ID RAB-ID, 

dl-GTP-PDU-SequenceNumber DL-GTP-PDU-SequenceNumber OPTIONAL, 

ul-GTP-PDU-SequenceNumber UL-GTP-PDU-SequenceNumber OPTIONAL, 

dl-N-PDU-SequenceNumber DL-N-PDU-SequenceNumber OPTIONAL, 

ul-N-PDU-SequenceNumber UL-N-PDU-SequenceNumber OPTIONAL, 

iE-Extensions ProtocolExtensionContainer ( ( RAB-Contextltem-ExtlEs-RANAP-RelocInf } } OPTIONAL, 

} 

RAB-Contextltem-ExtlEs-RANAP-RelocInf RANAP-PROTOCOL-EXTENSION ::= { 

} 

RANAP-RelocationlnformationExtensions RANAP-PROTOCOL-EXTENSION :;= { 

} 

************************************************************** 

— RAB MODIFICATION REQUEST ELEMENTARY PROCEDURE 

************************************************************** 

************************************************************** 

— RAB Modify Request 

************************************************************** 

RAB-ModifyRequest ::= SEQUENCE { 

protocolIEs ProtocolIE-Container ( ( RAB-Modif yRequestlEs } }, 

protocolExtensions ProtocolExtensionContainer { { RAB-Modif yRequestExtensions } } OPTIONAL, 

} 

RAB-ModifyRequestlEs RANAP-PROTOCOL-IES ::= { 

{ ID id-RAB-ModifyList CRITICALITY ignore TYPE RAB-Modif yList PRESENCE mandatory}, 

} 

RAB-ModifyList :;= RAB-IE-ContainerList ( ( RAB-Modif yItemlEs } } 

RAB-ModifyltemlEs RANAP-PROTOCOL-IES ::= { 

{ ID id-RAB-Modifyltem CRITICALITY ignore TYPE RAB-Modif yitem PRESENCE mandatory }, 

} 

RAB-Modifyltem ::= SEQUENCE { 

£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



169 



ETSI TS 125 413 V4.10.0 (2003-09) 



rAB-ID RAB-ID, 

requested-RAB-Parameter-Values Requested-RAB-Parameter-Values, 

iE-Extensions ProtocolExtensionContainer { ( RAB-Modif yItem-ExtlEs } } 



OPTIONAL, 



RAB-Modifyltem-ExtlEs RANAP-PROTOCOL-EXTENSION ::= { 



RAB-ModifyRequestExtensions RANAP-PROTOCOL-EXTENSION ::= { 



************************************************************** 



— LOCATION RELATED DATA ELEMENTARY PROCEDURE 

************************************************************** 



************************************************************** 



Location Related Data Request 



************************************************************** 



LocationRelatedDataRequest : := SEQUENCE ( 

protocolIEs ProtocolIE-Container { { LocationRelatedDataRequestlEs } }, 

protocolExtensions ProtocolExtensionContainer { { LocationRelatedDataRequestExtensions } } 



OPTIONAL, 



LocationRelatedDataRequestlEs RANAP-PROTOCOL-IES ::= { 

{ ID Id-LocationRelatedDataRequestType CRITICALITY reject TYPE LocationRelatedDataRequestType PRESENCE mandatory }, 



LocationRelatedDataRequestExtensions RANAP-PROTOCOL-EXTENSION ::= { 



************************************************************** 



— Location Related Data Response 



************************************************************** 



LocationRelatedDataResponse : := SEQUENCE ( 

protocolIEs ProtocolIE-Container { ( LocationRelatedDataResponselEs } }, 
protocolExtensions ProtocolExtensionContainer ( { LocationRelatedDataResponseExtensions } } 



OPTIONAL, 



LocationRelatedDataResponselEs RANAP-PROTOCOL-IES ::= { 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 170 ETSI TS 125 413 V4.10.0 (2003-09) 

{ ID id-BroadcastAssistanceDataDecipheringKeys CRITICALITY ignore TYPE BroadcastAssistanceDataDecipheringKeys PRESENCE optional } , 
} 
LocationRelatedDataResponseExtensions RANAP-PROTOCOL-EXTENSION ::= { 

} 

************************************************************** 

— Location Related Data Failure 

************************************************************** 

LocationRelatedDataFailure ::= SEQUENCE ( 

protocolIEs ProtocolIE-Container { ( LocationRelatedDataFailurelEs } }, 

protocolExtensions ProtocolExtensionContainer { { LocationRelatedDataFailureExtensions } } OPTIONAL, 

} 

LocationRelatedDataFailurelEs RANAP-PROTOCOL-IES ::= ( 

( ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory }, 

} 

LocationRelatedDataFailureExtensions RANAP-PROTOCOL-EXTENSION ::= { 

} 

END 

9.3.4 Information Element Definitions 

************************************************************** 

— Information Element Definitions 

************************************************************** 

RANAP-IEs ( 

itu-t (0) identif ied-organization (4) etsi (0) mobileDomain (0) 

umts-Access (20) modules (3) ranap (0) versionl (1) ranap-IEs (2) } 

DEFINITIONS AUTOMATIC TAGS ;;= 

BEGIN 

IMPORTS 

maxNr Of Errors, 

maxNrOfPDPDirections, 

maxNrOfPoints, 

maxNrOfRABs, 

maxNrOfSRBs, 

£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



171 



ETSI TS 125 413 V4.10.0 (2003-09) 



maxNrOf SeparateTraf f icDirections, 
maxRAB-Subf lows, 
maxRAB-SubflowCombi nation, 
maxNrOf Levels, 
maxNrOfAltValues, 

id-CN-Domain Indicator, 
id-MessageStructure, 
id-SRB-TrCH-Mapping, 
Id-TypeOfError 

FROM RANAP-Constants 

Criticality , 
ProcedureCode, 
ProtocolIE-ID, 
TriggeringMessage 
FROM RANAP-CommonDataTypes 

ProtocolExtensionContainer { } , 
RANAP-PROTOCOL-EXTENSION 
FROM RANAP-Containers; 

— A 

AllocationOrRetentionPriority ::= SEQUENCE { 
priorityLevel PriorityLevel, 

pre-empt ionCapability Pre-emptionCapability , 
pre-empt ionVulnerability Pre-empt ion Vulnerability, 
queuingAllowed QueuingAllowed, 

IE-Extensions ProtocolExtensionContainer { { AllocationOrRetentionPriority-ExtlEs } } OPTIONAL, 



AllocationOrRetentionPriority-ExtlEs RANAP-PROTOCOL-EXTENSION 



Alt-RAB-Parameters ::= SEQUENCE ( 

altMaxBitrateInf Alt-RAB-Parameter-MaxBitrateInf 

altGuaranteedBitRateInf Alt-RAB-Parameter-GuaranteedBitrateInf 
IE-Extensions ProtocolExtensionContainer ( (Alt-RAB-Parameters-ExtlEs } 



OPTIONAL, 

OPTIONAL, 

} OPTIONAL, 



Alt-RAB-Parameters-ExtlEs RANAP-PROTOCOL-EXTENSION ::= { 
} 

Alt-RAB-Parameter-GuaranteedBitrateInf ::= SEQUENCE { 

altGuaranteedBitrateType Alt-RAB-Parameter-GuaranteedBitrateType, 

al t Guar ant eedBit rates Alt-RAB-Parameter-Guar ant eedBit rates OPTIONAL 

— This IE shall be present if the Type of Guaranteed Bit Rates Information IE is set to "Value range" or "Discrete values" 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



172 



ETSI TS 125 413 V4.10.0 (2003-09) 



} 



Alt-RAB-Parameter-GuaranteedBitrateType 
unspecified, 
value-range, 
discrete-values, 



ENUMERATED { 



Alt-RAB-Parameter-GuaranteedBitrates ::= SEQUENCE (SIZE ( 1 . .maxNrOf AltValues) ) OF 
Alt-RAB-Parameter-GuaranteedBitrateList 

Alt-RAB-Parameter-GuaranteedBitrateList ::= SEQUENCE (SIZE ( 1 . . maxNrOf SeparateTraf f icDirections) ) OF GuaranteedBitrate 

Alt-RAB-Parameter-MaxBitrateInf ::= SEQUENCE { 

altMaxBitrateType Alt-RAB-Parameter-MaxBitrateType, 

altMaxBitrates Alt-RAB-Parameter-MaxBitrates OPTIONAL 

— This IE shall be present if the Type of Alternative Maxlmun Bit Rates Information IE is set to "Value range" or "Discrete values'' 



Alt-RAB-Parameter-MaxBitrateType : := ENUMERATED { 
unspecified, 
value-range, 
discrete-values. 



Alt-RAB-Parameter-MaxBitrates ::= SEQUENCE (SIZE ( 1 . .maxNrOf AltValues) ) OF 
Alt-RAB-Parameter-MaxBitrateList 

Alt-RAB-Parameter-MaxBitrateList ::= SEQUENCE (SIZE ( 1 . .maxNrOf SeparateTraf f icDirections) ) OF MaxBitrate 

Arealdentity ::= CHOICE { 
sAI SAI, 

geographical Are a GeographicalArea, 



Ass-RAB-Parameters ::= SEQUENCE { 

assMaxBitrateInf Ass-RAB-Parameter-MaxBitrateList OPTIONAL, 

assGuaranteedBitRateInf Ass-RAB-Parameter-GuaranteedBitrateList OPTIONAL, 

iE-Extensions ProtocolExtensionContainer ( ( Ass-RAB-Parameters-ExtlEs } } OPTIONAL, 



Ass-RAB-Parameters-ExtlEs RANAP-PROTOCOL-EXTENSION ::= { 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 173 ETSI TS 125 413 V4.10.0 (2003-09) 

Ass-RAB-Parameter-GuaranteedBitrateList ::= SEQUENCE (SIZE ( 1 . .maxNrOf SeparateTraf f icDirections) ) OF GuaranteedBitrate 
Ass-RAB-Parameter-MaxBitrateList ::= SEQUENCE (SIZE ( 1 . .maxNrOf SeparateTraf f icDirections) ) OF MaxBitrate 

— B 

BindingID ::= OCTET STRING (SIZE (4)) 

BroadcastAssistanceDataDecipheringKeys ::= SEQUENCE { 

cipheringKeyFlag BIT STRING (SIZE (1)), 

currentDecipheringKey BIT STRING (SIZE (56) ) , 

nextDecipheringKey BIT STRING (SIZE (56) ) , 

} 

— C 

Cause : := CHOICE { 

radioNetwork CauseRadioNetwork, 

transmissionNetwork CauseTransmissionNetwork, 

nAS CauseNAS, 

protocol CauseProtocol, 

misc CauseMisc, 

non-standard CauseNon-Standard, 

} 

CauseMisc ::= INTEGER { 

om-intervention (113), 

no-resource-available (114), 

unspecified-failure (115), 

network-optimisation (116) 
} (113. .128) 

CauseNAS ::= INTEGER ( 

user-restriction-start-indication (81) , 

user-restriction-end-indication (82) , 

normal-release (83) 
} (81. .96) 

CauseProtocol ::= INTEGER ( 

transfer-syntax-error (97), 
semantic-error (98), 

message-not-compatible-with-receiver-state (99) , 
abstract-syntax-error-reject (100) , 
abstract-syntax-error-ignore-and-notif y (101) , 
abstract-syntax-error-f alsely-constructed-message ( 102 ) 

} (97. .112) 

£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



174 



ETSI TS 125 413 V4.10.0 (2003-09) 



CauseRadioNetwork ::= INTEGER ( 

rab-pre-empted (1) , 

trelocoverall-expiry (2) , 

trelocprep-expiry (3) , 

treloccomplete-expiry (4) , 

tqueing-expiry (5) , 

relocation-triggered (6) , 

trellocalloc-expiry (7) , 

unable-to-establish-during-relocation (8) , 

unknown-target-rnc (9) , 

relocation-cancelled (10) , 

successful-relocation (11) , 

requested-ciphering-and-or-integrity-protect ion-algorithms -not -supported ( 12 ) , 

conf lict-with-already-existing-integrity-protection-and-or-ciphering-inf ormation (13) 

failure-in-the-radio-interf ace-procedure (14) , 

release-due-to-utran-generated-reason (15) , 

user-inactivity (16) , 

time-critical-relocation (17) , 

requested-traf f ic-class-not-available (18) , 

invalid-rab-parameters-value (19) , 

requested-maximum-bit-rate-not-available (20) , 

r eque sted-guar ant eed-bit -rate -not -available (21 ) , 

requested-transf er-delay-not-achievable (22) , 

invalid-rab-parameters-combination (23) , 

condition-violation-f or-sdu-parameters (24) , 

condit ion-violat ion- for-t raff ic-handling-pr lor ity (25) , 

condition-violation-f or-guar ant eed-bit -rate (2 6), 

user-plane-versions-not-supported (27) , 

iu-up-failure (28) , 

relocation-f allure -in-tar get -CN-RNC-or-tar get -system (29), 

invalid-RAB-ID (30) , 

no-remaining-rab (31) , 

interaction-with-other-procedure (32) , 

requested-maximum-bit-rate-f or-dl-not-available (33) , 

requested-maximum-bit-rate-f or-ul-not-available (34 ) , 

r equested-guaranteed-bit-r ate- f or-dl-not-available (35) , 

requested-guaranteed-bit-r ate- f or-ul-not-available (36) , 

repeated-integrity-checking-failure (37) , 

requested-request-type-not-supported (38) , 

request-superseded (39) , 

r elease -due -to-UE -gene r at ed-signal ling-connect ion-re lease ( 40 ) , 

resource-optimisation-relocation (41) , 

requested-inf ormation-not-available (42) , 

relocation-desirable-f or-radio-reasons (43) , 

relocation-not-supported-in-target-RNC-or-tar get -system ( 44 ) , 

directed-retry (45) , 

radio-connection-with-UE-Lost (46) , 

rNC-unable-to-establish-all-RFCs (47) , 

deciphering-keys-not-available (48) , 

dedicated-assistance-data-not-available (49) , 

relocation-target-not-allowed (50) , 

locat ion-report ing-congest ion (51 ) 
} (1..64) 



ETSI 



3GPP TS 25.413 version 4.10.0 Release 4 



175 



ETSI TS 125 413 V4.10.0 (2003-09) 



CauseNon-Standard ::= INTEGER (129.. 256) 
— Cause value 256 shall not be used — 

CauseTransmissionNetwork : := INTEGER { 

signalling-transport-resource-failure (65) , 
iu-transport-connection-f ailed-to-establish ( 6£: 

} (65. .80) 

ClientType ::= ENUMERATED { 
emergency-Services, 
value-Added-Services, 
pLMN-Operator-Services, 
lawful- Intercept -Services, 
pLMN-Oper at or-Broadcast -Services, 
pLMN-Operator-0-et-M, 
pLMN-Operator-Anonymous-Statistics, 
pLMN-Ope r at or-Tar get -MS -Service -Support, 



CriticalityDiagnostics : : 
procedureCode 
triggeringMessage 
procedureCriticality 



SEQUENCE ( 
ProcedureCode 
TriggeringMessage 
Criticality 



OPTIONAL, 
OPTIONAL, 
OPTIONAL, 



iEsCriticalityDiagnostics CriticalityDiagnostics-IE-List OPTIONAL, 

iE-Extensions ProtocolExtensionContainer { { CriticalityDiagnostics-ExtlEs } } OPTIONAL, 



} 



CriticalityDiagnostics-ExtlEs RANAP-PROTOCOL-EXTENSION ::= { 
} 

CriticalityDiagnostics-IE-List ::= SEQUENCE (SIZE ( 1 .. maxNrOf Errors) ) OF 
SEQUENCE ( 

iECriticality Criticality, 

iE-ID ProtocolIE-ID, 

repetitionNumber RepetitionNumberO OPTIONAL, 

iE-Extensions ProtocolExtensionContainer { { CriticalityDiagnostics-IE-List-ExtlEs } } OPTIONAL, 



CriticalityDiagnostics-IE-List-ExtlEs RANAP-PROTOCOL-EXTENSION ::= { 

— Extension for Release 99 to enable reporting the message structure down to the erroneous IE — 

{ ID id-MessageStructure CRITICALITY ignore EXTENSION MessageStructure PRESENCE optional } I 

— Extension for Release 99 to enable reporting if a reported error is due to a not understood or a missing IE 

( ID id-TypeOfError CRITICALITY ignore EXTENSION TypeOfError PRESENCE mandatory }, 



MessageStructure 
SEQUENCE { 
IE-ID 
repetitionNumber 



SEQUENCE (SIZE ( 1 . .maxNrOf Levels ) 



ProtocolIE-ID, 
RepetitionNumberl 



OF 



OPTIONAL, 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



176 



ETSI TS 125 413 V4.10.0 (2003-09) 



iE-Extensions 



ProtocolExtensionContainer ( (MessageStructure-ExtlEs } } OPTIONAL, 



MessageStructure-ExtlEs RANAP-PROTOCOL-EXTENSION ;;= { 
} 



CGI : := SEQUENCE { 
pLMNidentity 
lAC LAC , 

cl CI, 

iE-Extensions 



PLMNidentity, 



ProtocolExtensionContainer ( (CGI-ExtlEs} } OPTIONAL 



CGI-ExtlEs RANAP-PROTOCOL-EXTENSION ::= { 



ChosenEncryptionAlgorithm ::= EncryptionAlgorithm 
ChosenlntegrityProtectionAlgorithm : := IntegrityProtectionAlgorithm 
CI ::= OCTET STRING (SIZE (2)) 

ClassmarkInformation2 ::= OCTET STRING 

ClassmarkInformation3 ::= OCTET STRING 

CN-Domainlndicator : := ENUMERATED ( 

cs-domain, 

ps-domain 
} 



CN-ID 



INTEGER (0 . .4095) 



DataVolumeRef erence 



INTEGER (0 . .255) 



DataVolumeReportinglndication : := ENUMERATED { 
do-report, 
do-not -report 



DCH-ID ::= INTEGER (0..255) 

DeliveryOfErroneousSDU : := ENUMERATED { 
yes, 
no, 
no-error-detection-consideration 



} 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 177 ETSI TS 125 413 V4.10.0 (2003-09) 

DeliveryOrder : := ENUMERATED { 

delivery-order-requested, 

delivery-order-not -requested 
} 

DL-GTP-PDU-SequenceNumber ::= INTEGER (0.. 65535) 

— Reference: xx . xxx 

DL-N-PDU-SequenceNumber ::= INTEGER (0.. 65535) 

— Reference: xx . xxx 

D-RNTI :;= INTEGER (0.. 1048575) 

DRX-CycleLengthCoefficient ::= INTEGER (6.. 9) 

DSCH-ID ::= INTEGER (0..255) 

— E 

EncryptionAlgorithm ::= INTEGER ( no-encryption (0), standard-UMTS-encryption-algorith-UEAl (1) } (0..15) 

Encryptionlnformation : := SEQUENCE ( 

permittedAlgorithms PermittedEncryptionAlgorithms, 

key EncryptionKey , 

iE-Extensions ProtocolExtensionContainer ( ( Encryptioninf ormation-ExtlEs } } OPTIONAL 

} 

Encryptionlnformation-ExtlEs RANAP-PROTOCOL-EXTENSION ::= { 
} 

EncryptionKey ::= BIT STRING (SIZE (128)) 

— Reference: 33.102 

Event ::= ENUMERATED { 

stop-change -of -service -area, 

direct, 

change -of-servicearea, 

stop-direct 
} 

— F 

— G 

GeographicalArea ::= CHOICE { 

point GA-Point, 

pointWithUnCertainty GA-PointWithUnCertainty , 

polygon GA-Polygon, 

pointWithUncertaintyEllipse GA-PointWithUnCertaintyEllipse, 

pointWithAltitude GA-PointWithAltitude, 

pointWithAltitudeAndUncertaintyEllipsoid GA-PointWithAltitudeAndUncertaintyEllipsoid, 

£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



178 



ETSI TS 125 413 V4.10.0 (2003-09) 



ellipsoidArc 



GA-EllipsoidArc 



} 



GeographicalCoordinates ::= SEQUENCE { 

latitudeSign ENUMERATED ( north, south }, 

latitude INTEGER ( .. 8388 607 ) , 

longitude INTEGER (-8388 608 .. 8388 607 ) , 

iE-Extensions ProtocolExtensionContainer { { GeographicalCoordinates-ExtlEs } } OPTIONAL, 

} 

GeographicalCoordinates-ExtlEs RANAP-PROTOCOL-EXTENSION ::= { 
} 

GA-AltitudeAndDirection ::= SEQUENCE { 

directionOfAltitude ENUMERATED (height, depth}, 
altitude INTEGER (0.. 32767), 

} 



GA-EllipsoidArc ::= SEQUENCE { 

geographicalCoordinates GeographicalCoordinates, 

innerRadius 

uncertainty Radius 

of f setAngle 

includedAngle 

confidence 

iE-Extensions 



INTEGER 





.655 


INTEGER 





.127 


INTEGER 





.179 


INTEGER 





.179 


INTEGER 





.127 



ProtocolExtensionContainer ( ( GA-EllipsoidArc-ExtlEs } } OPTIONAL, 



GA-EllipsoidArc-ExtlEs RANAP-PROTOCOL-EXTENSION ::= { 



GA-Point ::= SEQUENCE ( 

geographicalCoordinates GeographicalCoordinates, 

iE-Extensions ProtocolExtensionContainer ( ( GA-Point-ExtlEs } } OPTIONAL, 



GA-Point-ExtlEs RANAP-PROTOCOL-EXTENSION ::= { 



GA-PointWithAltitude ::= SEQUENCE ( 

geographicalCoordinates GeographicalCoordinates, 
altitudeAndDirection GA-AltitudeAndDirection, 
iE-Extensions ProtocolExtensionContainer ( ( GA-PointWithAltitude-ExtlEs } } OPTIONAL, 



GA-PointWithAltitude-ExtlEs RANAP-PROTOCOL-EXTENSION :;= { 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 179 ETSI TS 125 413 V4.10.0 (2003-09) 



GA-PointWithAltitudeAndUncertaintyEllipsoid ::= SEQUENCE { 

geographicalCoordinates GeographicalCoordinates, 

altitudeAndDir action GA-AltitudeAndDirection, 

uncertaintyEllipse GA-UncertaintyEllipse, 

uncertaintyAltitude INTEGER (0..127), 

confidence INTEGER (0..127), 

iE-Extensions ProtocolExtensionContainer ( ( GA-PointWithAltitudeAndUncertaintyEllipsoid-ExtlEs } } OPTIONAL, 

} 

GA-PointWithAltitudeAndUncertaintyEllipsoid-ExtlEs RANAP-PROTOCOL-EXTENSION ;;= { 
} 

GA-PointWithUnCertainty ::=SEQUENCE { 

geographicalCoordinates GeographicalCoordinates, 

iE-Extensions ProtocolExtensionContainer ( ( GA-PointWithUnCertainty-ExtlEs } } OPTIONAL, 

uncertaintyCode INTEGER (0..127) 

} 

GA-PointWithUnCertainty-ExtlEs RANAP-PROTOCOL-EXTENSION ;;= { 
} 

GA-PointWithUnCertaintyEllipse ::= SEQUENCE { 

geographicalCoordinates GeographicalCoordinates, 

uncertaintyEllipse GA-UncertaintyEllipse, 

confidence INTEGER (0..127), 

iE-Extensions ProtocolExtensionContainer ( ( GA-PointWithUnCertaintyEllipse-ExtlEs } } OPTIONAL, 

} 

GA-PointWithUnCertaintyEllipse-ExtlEs RANAP-PROTOCOL-EXTENSION ::= { 
} 

GA-Polygon ;;= SEQUENCE (SIZE ( 1 .. maxNrOf Points) ) OF 
SEQUENCE { 

geographicalCoordinates GeographicalCoordinates, 

iE-Extensions ProtocolExtensionContainer ( ( GA-Polygon-ExtlEs } } OPTIONAL, 

} 

GA-Polygon-ExtlEs RANAP-PROTOCOL-EXTENSION ::= { 
} 

GA-UncertaintyEllipse ::= SEQUENCE { 

uncertaintySemi-major INTEGER (0..127), 

uncertaintySemi-minor INTEGER (0..127), 

orientationOfMajorAxis INTEGER (0..179), — The values 90.. 179 shall not be used. 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



180 



ETSI TS 125 413 V4.10.0 (2003-09) 



} 



GlobalCN-ID ::= SEQUENCE { 
pLMNidentity 
CN-ID CN-ID 



PLMNidentity, 



GlobalRNC-ID ::= SEQUENCE { 

pLMNidentity PLMNidentity, 

rNC-ID RNC-ID 



GTP-TEI 

— Reference: xx . xxx 



OCTET STRING (SIZE (' 



Guar ant eedBit rate 

— Unit is bits per sec 



:;= INTEGER ( .. 1 6000000 ) 



IMEI ::= OCTET STRING (SIZE {i 

— Reference: 23.003 



IMS I 

— Reference: 23.003 



TBCD-STRING (SIZE (3. 



IntegrityProtectionAlgorithm : := INTEGER { 

standard-UMTS-integrity-algorithm-UIAl (0) , 

no-value (15) 
} (0..15) 

IntegrityProtectionlnformation : := SEQUENCE ( 

permittedAlgorithms PermittedlntegrityProtectionAlgorithms, 

key IntegrityProtectionKey , 

IE-Extensions ProtocolExtensionContainer { { IntegrityProtectionInf ormation-ExtlEs } } OPTIONAL 

} 

IntegrityProtectionlnformation-ExtlEs RANAP-PROTOCOL-EXTENSION ::= { 



IntegrityProtectionKey ::= 

luSignallingConnect ion Identifier 

luTransportAssociation : := CHOICE ( 
gTP-TEI GTP-TEI, 

bindingID BindingID, 



BIT STRING (SIZE (128)) 
:;= BIT STRING (SIZE (24) 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



181 



ETSI TS 125 413 V4.10.0 (2003-09) 



— J 

— K 

KeyStatus ::= ENUMERATED { 
old, 
new, 



— L 

LAC 

LAI : := SEQUENCE { 
pLMNidentity 
lAC LAC , 

iE-Extensions 



OCTET STRING (SIZE (2)) 

PLMNidentity, 
ProtocolExtensionContainer ( {LAI-ExtlEs} } OPTIONAL 



LAI-ExtlEs RANAP-PROTOCOL-EXTENSION ::= { 



LastKnownServiceArea ::= SEQUENCE { 
sAI SAI, 

ageOfSAI INTEGER (0.. 327 67), 
iE-Extensions ProtocolExtensionContainer { { LastKnownServiceArea-ExtlEs } } OPTIONAL, 



LastKnownServiceArea-ExtlEs RANAP-PROTOCOL-EXTENSION ;;= { 
} 

LocationRelatedDataRequestType : := SEQUENCE { 

requestedLocationRelatedDataType RequestedLocationRelatedDataType, 

requestedGPSAssistanceData RequestedGPSAssistanceData OPTIONAL, 

— This IE shall be present if the Requested Location Related Data Type IE is set to ^Dedicated Assistance Data for Assisted GPS' 



L3-Inf ormation 

— M 

MaxBitrate 

— Unit is bits per sec 

MaxSDU-Size 

— MaxSDU-Size 

— Unit is bit 



OCTET STRING 



INTEGER (1 . . 16000000) 



INTEGER (0 . .3276S 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



182 



ETSI TS 125 413 V4.10.0 (2003-09) 



— N 



NAS-PDU ::= OCTET STRING 

NAS-Synchronisationlndicator ::= BIT STRING (SIZE (4) 

NonSearchinglndication : := ENUMERATED ( 
non-searching, 
searching 



NumberOf lulnstances 
NumberOf Steps 

— 
OldBSS-ToNewBSS-Information 

OMC-ID 

— Reference: GSM [25] 



INTEGER (1 . .2) 
INTEGER (1 . .16) 

: := OCTET STRING 
OCTET STRING (SIZE (3.. 22)) 



PagingArealD ::= CHOICE { 
lAI LAI, 

rAI RAI, 



PagingCause ::= ENUMERATED { 

t erminating-conver sat ional -call, 
terminating-streaming-call, 
terminating-inter active -call, 
terminating-background-call, 
terminating-low-priority-signalling, 

terminating-high-priority-signalling 



PDP-Typelnformation ::= SEQUENCE (SIZE ( 1 . .maxNrOf PDPDirections) ) OF 
PDP-Type 

PDP-Type ::= ENUMERATED { 
empty, 
PPP- 

osp-ihoss — this value shall not be used — , 
ipv4 , 
ipv6. 



PermanentNAS-UE-ID 



CHOICE { 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



IMS I, 



183 



ETSI TS 125 413 V4.10.0 (2003-09) 



PermittedEncryptionAlgorithms 
Encrypt ionAlgorithm 



SEQUENCE (SIZE (1..16)) OF 



PermittedlntegrityProtectionAlgorithms ::= SEQUENCE (SIZE (1..16)) OF 
IntegrityProtect ionAlgorithm 



PLMNidentity 

PositioningPriority 
high-Priority, 
normal-Priority, 



} 



::= TBCD-STRING (SIZE (3) 
ENUMERATED { 



Pre-emptionCapability ::= ENUMERATED { 
shall -not -trigger-pre-empt ion, 
may-trigger-pre-emption 



Pre-empt ion Vulnerability 
not -pre-empt able, 
pre-emptable 



ENUMERATED { 



PriorityLevel 

P-TMSI 

— Q 



:;= INTEGER ( spare (0), highest (1), lowest (14), no-priority (15) } (0..15) 
OCTET STRING (SIZE (4)) 



QueuingAllowed ::= ENUMERATED { 
queueing-not-allowed, 
queueing-allowed 



} 



R 



RAB-Asymmetry Indicator : := ENUMERATED { 
symmetric-bidirectional, 
asymmetric-unidirectional-downlink, 
asymmetric-unidirectional-uplink, 
asymmetric-bidirectional. 



RAB-ID :;= BIT STRING (SIZE (8)) 

RAB-Parameter-GuaranteedBitrateList ::= SEQUENCE (SIZE ( 1 . .maxNrOf SeparateTraf f icDirections) ) OF GuaranteedBitrate 

RAB-Parameter-MaxBitrateList ::= SEQUENCE (SIZE ( 1 . .maxNrOf SeparateTraf f icDirections) ) OF MaxBitrate 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



184 



ETSI TS 125 413 V4.10.0 (2003-09) 



RAB-Parameters ::= SEQUENCE { 

trafficClass Traf f icClass, 

rAB -Asymmetry Indicator RAB -Asymmetry Indicator, 



maxBitrate 

guar ant eedBit Rate 



RAB-Parameter-MaxBitrateList, 

RAB-Parameter-GuaranteedBitrateList 



— This IE shall be present the traffic class IE is set to 



OPTIONAL 
Conversational'' 



or "Streaming" — , 



delivery Order 
maxSDU-Size 
sDU-Parameters 
transferDelay 
— This IE shall 



Delivery Order, 
MaxSDU-Size, 

SDU-Parameters, 
TransferDelay OPTIONAL 
be present the traffic class IE is set to "Conversational" or "Streaming" 
traf ficHandlingPriority Traf f icHandlingPriority OPTIONAL 

— This IE shall be present the traffic class IE is set to "Interactive" — , 
allocationOrRetentionPriority AllocationOrRetentionPriority OPTIONAL, 
sourceStatisticsDescriptor SourceStatisticsDescriptor OPTIONAL 

— This IE shall be present the traffic class IE is set to "Conversational" or "Streaming" 
relocationRequirement RelocationRequirement OPTIONAL, 

IE-Extensions ProtocolExtensionContainer ( { RAB-Parameters-ExtlEs } } OPTIONAL, 



} 

RAB-Parameters-ExtlEs RANAP-PROTOCOL-EXTENSION ::= { 

} 

RAB-SubflowCombinationBitRate ::= INTEGER ( .. 1 6000000 ) 

RAB-TrCH-Mapping ::= SEQUENCE ( SIZE ( 1 . .maxNrOf RABs) ) OF 
RAB-TrCH-Mappingltem 

RAB-TrCH-Mappingltem ::= SEQUENCE { 
rAB-ID RAB-ID, 

trCH-ID-List TrCH-ID-List , 
IE-Extensions ProtocolExtensionContainer ( { RAB-TrCH-Mappingltem-ExtlEs } } OPTIONAL, 



RAB-TrCH-Mappingltem-ExtlEs RANAP-PROTOCOL-EXTENSION ::= { 

— Extension for Release 99 to enable transfer of RAB Subflow mapping onto lur transport channel Ids for a given indicated domain 
( ID id-CN-Domainlndicator CRITICALITY ignore EXTENSION CN-Domainlndicator PRESENCE optional}. 



RAC 
RAI 



OCTET STRING (SIZE (1) 



; := SEQUENCE ( 

lAI LAI, 

r AC RAC , 

iE-Extensions 



ProtocolExtensionContainer ( (RAI-ExtlEs} } OPTIONAL, 



RAI-ExtlEs RANAP-PROTOCOL-EXTENSION 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



185 



ETSI TS 125 413 V4.10.0 (2003-09) 



} 



RateControlAllowed : := ENUMERATED { 

not-allowed, 

allowed 
} 

RelocationRequirement : := ENUMERATED { 
lossless, 
none, 

realtime 



RelocationType : := ENUMERATED ( 
ue -not -involved, 
ue-involved. 



RepetitionNumberO 
RepetitionNumberl 



INTEGER (0 . .255) 
INTEGER (1 . .256) 



ReportArea : := ENUMERATED { 
service-area, 
geographical -area. 



RequestedGPSAssistanceData ::= OCTET STRING (SIZE (1 .. 3S 
— gpsAssistanceData as defined in 24.080 — 

RequestedLocationRelatedDataType : := ENUMERATED { 
decipher ingKeysUEBasedOTDOA, 
decipher ingKeysAs si St edGPS, 
dedicatedAssistanceDataUEBasedOTDOA, 
dedicatedAssistanceDataAssistedGPS, 



Requested-RAB-Parameter-Values : := SEQUENCE { 

requestedMaxBit rates Requested-RAB-Parameter-MaxBitrateList OPTIONAL, 

requestedGuar ant eedBit rates Requested-RAB-Parameter-GuaranteedBitrateList OPTIONAL, 

IE-Extensions ProtocolExtensionContainer ( ( Requested-RAB-Parameter-Values-ExtlEs } } OPTIONAL, 



Requested-RAB-Parameter-Values-ExtlEs RANAP-PROTOCOL-EXTENSION ::= { 

} 

Requested-RAB-Parameter-MaxBitrateList ::= SEQUENCE (SIZE ( 1 . .maxNrOf SeparateTraf f icDirections) ) OF MaxBitrate 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 186 ETSI TS 125 413 V4.10.0 (2003-09) 

Requested-RAB-Parameter-GuaranteedBitrateList ::= SEQUENCE (SIZE ( 1 . . maxNrOf SeparateTraf f icDirections) ) OF GuaranteedBitrate 

RequestType ::= SEQUENCE ( 

event Event, 

reportArea ReportArea, 

accuracyCode INTEGER (0..127) OPTIONAL, 

} 

ResidualBitErrorRatio ::= SEQUENCE { 

mantissa INTEGER (1..9), 

exponent INTEGER (1..8), 

iE-Extensions ProtocolExtensionContainer ( ( ResidualBitErrorRatio-ExtlEs } } OPTIONAL 

} 

— ResidualBitErrorRatio = mantissa * lO'^-exponent 

ResidualBitErrorRatio-ExtlEs RANAP-PROTOCOL-EXTENSION ::= { 

} 

ResponseTime : := ENUMERATED { 
lowdelay , 
delaytolerant, 

} 

RNC-ID :;= INTEGER (0..4095) 

— RNC-ID ::= BIT STRING (SIZE (12)) 

— Harmonized with RNSAP and NBAP definitions 

RRC-Container ::= OCTET STRING 

— S 

SAC ::= OCTET STRING (SIZE (2)) 

SAI : := SEQUENCE { 

pLMNidentity PLMNidentity , 

lAC LAC , 

sAC SAC, 

iE-Extensions ProtocolExtensionContainer ( (SAI-ExtlEs} } OPTIONAL 

} 

SAI-ExtlEs RANAP-PROTOCOL-EXTENSION ::= { 

} 

SAPI ;;= ENUMERATED { 
sapi-0 , 
sapi-3, 

} 

£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 187 ETSI TS 125 413 V4.10.0 (2003-09) 

SDU-ErrorRatio ::= SEQUENCE { 

mantissa INTEGER (1..9), 

exponent INTEGER (1..6), 

IE-Extensions ProtocolExtensionContainer ( ( SDU-ErrorRatio-ExtlEs } } OPTIONAL 

} 
— SDU-ErrorRatio = mantissa * lO'^-exponent 

SDU-ErrorRatio-ExtlEs RANAP-PROTOCOL-EXTENSION ::= { 

} 

SDU-FormatlnformationParameters ::= SEQUENCE (SIZE ( 1 . . maxRAB-Subf lowCombination) ) OF 
SEQUENCE ( 

subflowSDU-Size Subf lowSDU-Size OPTIONAL, 

rAB-SubflowCombinationBitRate RAB-Subf lowCombinationBitRate OPTIONAL, 

iE-Extensions ProtocolExtensionContainer { { SDU-FormatlnformationParameters-ExtlEs } } OPTIONAL, 

} 

SDU-FormatlnformationParameters-ExtlEs RANAP-PROTOCOL-EXTENSION :;= { 
} 

SDU-Parameters ::= SEQUENCE (SIZE ( 1 . .maxRAB-Subf lows) ) OF 
SEQUENCE { 

sDU-ErrorRatio SDU-ErrorRatio OPTIONAL 

— This IE shall be present if the Delivery Of Erroneous SOU IE is set to "Yes" or "No" — , 

residualBitErrorRatio ResidualBitErrorRatio, 

deli very Of ErroneousSDU DeliveryOfErroneousSDU, 

sDU-FormatlnformationParameters SDU-FormatlnformationParameters OPTIONAL, 

iE-Extensions ProtocolExtensionContainer ( ( SDU-Parameters-ExtlEs } } OPTIONAL, 

} 

SDU-Parameters-ExtlEs RANAP-PROTOCOL-EXTENSION ::= { 
} 

Service-Handover : := ENUMERATED ( 

handover-to-GSM-should-be -per formed, 
handover-to-GSM-should-not -be -per formed, 
handover-to-GSM-shall -not -be -per formed, 

} 

SourcelD : := CHOICE { 

sourceRNC-ID SourceRNC-ID, 

sAI SAI, 

} 

SourceRNC-ID ::= SEQUENCE { 

pLMNidentity PLMNidentity , 

£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 188 ETSI TS 125 413 V4.10.0 (2003-09) 

rNC-ID RNC-ID, 

iE-Extensions ProtocolExtensionContainer ( ( SourceRNC-ID-ExtlEs } } OPTIONAL 

} 

SourceRNC-ID-ExtlEs RANAP-PROTOCOL-EXTENSION ::= { 
} 

SourceRNC-ToTargetRNC-TransparentContainer ::= SEQUENCE { 
rRC-Container RRC-Container, 

numberOflu Instances NumberOflu Instances, 
relocationType RelocationType, 

chosenlntegrityProtectionAlgorithm ChosenlntegrityProtectionAlgorithm OPTIONAL, 
integrityProtectionKey IntegrityProtectionKey OPTIONAL, 

chosenEncryptionAlgorithFor Signal ling ChosenEncryptionAlgorithm OPTIONAL, 
cipheringKey EncryptionKey OPTIONAL, 

chosenEncryptionAlgorithForCS ChosenEncryptionAlgorithm OPTIONAL, 
ChosenEncryptionAlgorithFor PS ChosenEncryptionAlgorithm OPTIONAL, 
d-RNTI D-RNTI OPTIONAL 

— This IE shall be present if the Relocation type IE is set to "UE not involved in relocation of SRNS" — , 
targetCellld TargetCellld OPTIONAL 

— This IE shall be present if the Relocation type IE is set to "UE involved in relocation of SRNS" — , 
rAB-TrCH-Mapping RAB-TrCH-Mapping OPTIONAL, 

iE-Extensions ProtocolExtensionContainer ( ( SourceRNC-ToTargetRNC-TransparentContainer-ExtlEs } } OPTIONAL, 

} 

SourceRNC-ToTargetRNC-TransparentContainer-ExtlEs RANAP-PROTOCOL-EXTENSION ::= { 

— Extension for Release 99 to enable transfer of SRB mapping onto lur transport channel Ids -- 

( ID id-SRB-TrCH-Mapping CRITICALITY reject EXTENSION SRB-TrCH-Mapping PRESENCE optional }, 

} 

SourceStatisticsDescriptor : := ENUMERATED { 
speech, 
unknown, 

} 

SRB-ID ::= INTEGER (1..32) 

SRB-TrCH-Mapping ::= SEQUENCE ( SIZE ( 1 . .maxNrOf SRBs) ) OF 
SRB-TrCH-Mappingltem 

SRB-TrCH-Mappingltem ::= SEQUENCE ( 
sRB-ID SRB-ID, 

trCH-ID TrCH-ID, 

iE-Extensions ProtocolExtensionContainer { { SRB-TrCH-Mappingltem-ExtlEs } } OPTIONAL, 

} 

SRB-TrCH-Mappingltem-ExtlEs RANAP-PROTOCOL-EXTENSION ::= { 

£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



189 



ETSI TS 125 413 V4.10.0 (2003-09) 



SubflowSDU-Size 
— Unit is bit 



INTEGER (0 . .4095) 



— T 

TargetCellld 

TargetID : := CHOICE { 
targetRNC-ID 
cGI CGI, 



INTEGER (0 . .268435455) 



TargetRNC-ID, 



TargetRNC-ID ::= SEQUENCE { 
lAI LAI, 

rAC RAC OPTIONAL 

— Must always be present towards the PS domain and never towards the CS domain — , 
rNC-ID RNC-ID, 

iE-Extensions ProtocolExtensionContainer ( ( TargetRNC-ID-ExtlEs } } OPTIONAL 



TargetRNC-ID-ExtlEs RANAP-PROTOCOL-EXTENSION ::= { 



TargetRNC-ToSourceRNC-TransparentContainer ::= SEQUENCE { 
rRC-Container RRC-Container , 

d-RNTI D-RNTI OPTIONAL 

— May be included to allow the triggering of the Relocation Detect procedure from the lur Interface — , 
iE-Extensions ProtocolExtensionContainer ( ( TargetRNC-ToSourceRNC-TransparentContainer-ExtlEs } } OPTIONAL, 



TargetRNC-ToSourceRNC-TransparentContainer-ExtlEs RANAP-PROTOCOL-EXTENSION 



TBCD-STRING 



OCTET STRING 



TemporaryUE-ID ::= CHOICE { 

tMSI TMSI, 

p-TMSI P-TMSI, 



TMSI 



::= OCTET STRING (SIZE (' 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



190 



ETSI TS 125 413 V4.10.0 (2003-09) 



Trace Reference 

TraceType : : = 

— Reference: GSM TS 12.08 



::= OCTET STRING (SIZE (2.. 3) 
OCTET STRING (SIZE (1)) 



TrafficClass ::= ENUMERATED { 
conversational, 
streaming, 
interactive, 
background, 



TrafficHandlingPriority 

TransferDelay 

— Unit is millisecond 



::= INTEGER ( spare (0), highest (1), lowest (14), no-priority-used (15) } (0..15) 
; ;= INTEGER (0 . . 65535) 



UnsuccessfullyTransmittedDataVolume ::= INTEGER ( . . 42 94 9672 95) 

TransportLayerAddress ::= BIT STRING (SIZE (1..160, ...)) 

TrCH-ID ::= SEQUENCE ( 

dCH-ID DCH-ID OPTIONAL, 

dSCH-ID DSCH-ID OPTIONAL, 

uSCH-ID USCH-ID OPTIONAL, 
IE-Extensions ProtocolExtensionContainer ( ( TrCH-ID-ExtlEs } } OPTIONAL, 



TrCH-ID-ExtlEs RANAP-PROTOCOL-EXTENSION 



TrCH-ID-List 
TrCH-ID 

TriggerlD 



SEQUENCE (SIZE ( 1 . . maxRAB-Subf lows ) ) OF 



OCTET STRING (SIZE (3.. 22)) 



TypeOf Error ::= ENUMERATED { 
not-understood, 
missing. 



UE- 


-ID :: = 


CHOICE { 






imsi 




IMSI 




imei 




IMEI 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



191 



ETSI TS 125 413 V4.10.0 (2003-09) 



UL-GTP-PDU-SequenceNumber 
UL-N-PDU-SequenceNumber 
UP -Mode Vers ions 
USCH-ID 



: := INTEGER (0 . . 65535) 
: := INTEGER (0 . . 65535) 
;;= BIT STRING (SIZE (16)) 
: := INTEGER (0 . .255) 



UserPlaneMode ::= ENUMERATED { 
transparent -mode, 
support-mode-f or-predef ined-SDU-sizes, 



— V 

Vertical Ac curacyCode 



: ;= INTEGER (0 . . 127) 



END 



9.3.5 Common Definitions 



************************************************************** 

— Common definitions 

************************************************************** 

RANAP-CommonDataTypes ( 

itu-t (0) identif ied-organization (4) etsi (0) mobileDomain (0) 

umts-Access (20) modules (3) ranap (0) versionl (1) ranap-CommonDataTypes (3) } 

DEFINITIONS AUTOMATIC TAGS ::= 

BEGIN 



Criticality 

Presence 

PrivatelE-ID 
local 
global 



ENUMERATED { reject, ignore, notify } 

ENUMERATED { optional, conditional, mandatory } 

CHOICE { 

INTEGER (0 . . 65535) , 
OBJECT IDENTIFIER 



ProcedureCode 

ProtocolExtensionID 

ProtocolIE-ID 



INTEGER (0 . .255) 
INTEGER (0 . . 65535) 
INTEGER (0 . .65535) 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



192 



ETSI TS 125 413 V4.10.0 (2003-09) 



TriggeringMessage ::= ENUMERATED ( initiating-message, successful-outcome, unsuccessf ull-outcome, outcome } 
END 



9.3.6 Constant Definitions 



************************************************************** 

— Constant definitions 

************************************************************** 

RANAP-Constants ( 

itu-t (0) identif ied-organization (4) etsi (0) mobileDomain (0) 

umts-Access (20) modules (3) ranap (0) versionl (1) ranap-Constants (4) } 

DEFINITIONS AUTOMATIC TAGS ::= 

BEGIN 

************************************************************** 



Elementary Procedures 



************************************************************** 



id-RAB-Assignment 

id-Iu-Release 

id-Re locationP reparation 

id-RelocationRe source Alio cat ion 

id-RelocationCancel 

id-SRNS-ContextTransfer 

id-SecurityModeControl 

id-DataVolumeReport 

id-Reset 

id-RAB-ReleaseRequest 

id-Iu-ReleaseRequest 

id-RelocationDetect 

id-RelocationComplete 

id-Paging 

id-CommonID 

Id-CN-InvokeTrace 

Id-LocationReportingControl 

Id-LocationReport 

id- I nitialUE -Message 

id-DirectTransfer 

id-Over loadControl 

id-Err or Indication 

id-SRNS-DataForward 

id-ForwardSRNS-Context 

id-pri vat eMes sage 

Id-CN-DeactivateTrace 

id-Re set Re source 



INTEGER ; 


: = 





INTEGER ; 


: = 


1 


INTEGER : 


: = 


2 


INTEGER : 


: = 


3 


INTEGER ; 


; = 


4 


INTEGER ; 


: = 


5 


INTEGER ; 


: = 


6 


INTEGER ; 


: = 


7 


INTEGER ; 


: = 


9 


INTEGER ; 


: = 


10 


INTEGER ; 


; = 


11 


INTEGER ; 


: = 


12 


INTEGER ; 


: = 


13 


INTEGER ; 


: = 


14 


INTEGER ; 


: = 


15 


INTEGER ; 


: = 


16 


INTEGER ; 


: = 


17 


INTEGER ; 


: = 


18 


INTEGER ; 


: = 


19 


INTEGER ; 


: = 


20 


INTEGER ; 


: = 


21 


INTEGER ; 


: = 


22 


INTEGER ; 


: = 


23 


INTEGER ; 


: = 


24 


INTEGER ; 


: = 


25 


INTEGER ; 


: = 


26 


INTEGER : 


: = 


27 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



193 



ETSI TS 125 413 V4.10.0 (2003-09) 



id-RANAP -Re location 
id-RAB-Modify Request 
id-LocationRelatedData 



INTEGER 
INTEGER 
INTEGER 



28 
29 
30 



************************************************************** 



Extension constants 



************************************************************** 



maxPrivatelEs 
maxProtocolExt ens ions 
maxProtocolIEs 



INTEGER : 


= 65535 


INTEGER : 


= 65535 


INTEGER : 


= 65535 



************************************************************** 



— Lists 



************************************************************** 



maxNrOfDTs 

maxNr Of Errors 

maxNrOf luSigConlds 

maxNrOfPDPDirections 

maxNr Of Points 

maxNrOfRABs 

maxNrOf SeparateTraf f icDirections 

maxNrOfSRBs 

maxNrOfVol 

maxNrOf Levels 

maxNr Of Alt Values 



INTEGER : 


: = 


15 


INTEGER ; 


: = 


256 


INTEGER ; 


: = 


250 


INTEGER ; 


: = 


2 


INTEGER ; 


: = 


15 


INTEGER : 


: = 


256 


INTEGER : 


: = 


2 


INTEGER ; 


: = 


8 


INTEGER ; 


: = 


2 


INTEGER ; 


: = 


256 


INTEGER : 


; = 


16 



maxRAB-Sub flows 
maxRAB-SubflowCombi nation 



INTEGER : := 7 
INTEGER : := 64 



************************************************************** 



lEs 



************************************************************** 



id-Arealdentity 
id-CN-Domain Indicator 
id-Cause 

id-ChosenEncryptionAlgorithm 
id-Chosen Integrity? rot ectionAlgorithm 
id-ClassmarkInf ormation2 
id-ClassmarkInf ormation3 
id-CriticalityDiagnostics 
id-DL-GTP-PDU-SequenceNumber 
id-EncryptionInf ormation 
id-IntegrityProtectionInf ormation 
id-IuTransportAssociation 



INTEGER : 


: = 





INTEGER ; 


: = 


3 


INTEGER ; 


: = 


4 


INTEGER ; 


; = 


5 


INTEGER ; 


; = 


6 


INTEGER ; 


: = 


7 


INTEGER ; 


: = 


8 


INTEGER ; 


: = 


9 


INTEGER ; 


: = 


10 


INTEGER ; 


: = 


11 


INTEGER ; 


: = 


12 


INTEGER : 


: = 


13 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



194 



ETSI TS 125 413 V4.10.0 (2003-09) 



id-L3-Inf ormation 

id-LAI 

id-NAS-PDU 

id-NonSearchinglndication 

id-NumberOf Steps 

id-OMC-ID 

id-OldBSS-ToNewBSS-Inf ormation 

id-PagingArealD 

id-PagingCause 

id-PermanentNAS-UE-ID 

id-RAB-Contextltem 

id-RAB-ContextList 

id-RAB-DataForwardingltem 

id-RAB-DataForwardingltem-SRNS-CtxReq 

id-RAB-DataForwardingList 

id-RAB-DataForwardingList-SRNS-CtxReq 

id-RAB-DataVolumeReportltem 

id-RAB-DataVolumeReportList 

id-RAB-DataVolumeReportRequestltem 

Id-RAB-DataVolumeReportRequestList 

id-RAB-Failedltem 

id-RAB-FailedList 

id-RAB-ID 

id-RAB-Queuedltem 

id-RAB-QueuedList 

id-RAB-ReleaseFailedList 

id-RAB-Re lease I tern 

id-RAB-ReleaseList 

id-RAB-Releasedltem 

id-RAB-Re leasedLi St 

id-RAB-ReleasedList-IuRelComp 

id-RAB-Re locationRe lease I tern 

id-RAB-Re locationReleaseLi St 

id-RAB-SetupItem-RelocReq 

id-RAB-SetupItem-RelocReqAck 

id-RAB-SetupList-RelocReq 

id-RAB-SetupList-RelocReqAck 

id-RAB-SetupOrModifiedltem 

id-RAB-SetupOrModifiedList 

id-RAB-SetupOrModifyltem 

id-RAB-SetupOrModifyList 

id-RAC 

id-Re locationType 

id-Request Type 

id-SAI 

id-SAPI 

id-SourcelD 

id-Sour ceRNC-ToTargetRNC-Transparent Container 

id-TargetID 

id-Tar getRNC-ToSourceRNC-Transparent Container 

id-TemporaryUE-ID 

id-TraceRef erence 

id-TraceType 

Id-TransportLayerAddress 



INTEGER : 


:= 14 


INTEGER : 


:= 15 


INTEGER ; 


:= 16 


INTEGER ; 


:= 17 


INTEGER : 


:= 18 


INTEGER ; 


:= 19 


INTEGER ; 


:= 20 


INTEGER ; 


:= 21 


INTEGER ; 


:= 22 


INTEGER ; 


:= 23 


INTEGER ; 


:= 24 


INTEGER ; 


:= 25 


INTEGER ; 


:= 26 


INTEGER ; 


:= 27 


INTEGER ; 


:= 28 


INTEGER ; 


:= 29 


INTEGER ; 


:= 30 


INTEGER ; 


:= 31 


INTEGER ; 


:= 32 


INTEGER ; 


:= 33 


INTEGER ; 


:= 34 


INTEGER ; 


:= 35 


INTEGER ; 


:= 36 


INTEGER ; 


:= 37 


INTEGER ; 


:= 38 


INTEGER ; 


:= 39 


INTEGER ; 


:= 40 


INTEGER ; 


:= 41 


INTEGER ; 


:= 42 


INTEGER ; 


:= 43 


INTEGER : 


;= 44 


INTEGER : 


:= 45 


INTEGER ; 


:= 46 


INTEGER ; 


:= 47 


INTEGER ; 


:= 48 


INTEGER ; 


:= 49 


INTEGER ; 


:= 50 


INTEGER ; 


:= 51 


INTEGER ; 


:= 52 


INTEGER ; 


:= 53 


INTEGER ; 


:= 54 


INTEGER ; 


:= 55 


INTEGER ; 


:= 56 


INTEGER ; 


:= 57 


INTEGER ; 


:= 58 


INTEGER ; 


:= 59 


INTEGER ; 


:= 60 


INTEGER ; 


:= 61 


INTEGER : 


:= 62 


INTEGER : 


:= 63 


INTEGER : 


:= 64 


INTEGER ; 


:= 65 


INTEGER ; 


:= 66 


INTEGER : 


:= 67 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



195 



ETSI TS 125 413 V4.10.0 (2003-09) 



id-Trigger ID 

id-UE-ID 

id-UL-GTP-PDU-SequenceNumber 

id-RAB-FailedtoReportltem 

id-RAB-FailedtoReportList 

id-KeyStatus 

id-DRX-CycleLengthCoef f icient 

id-IuSigConldList 

id-IuSigConldltem 

id-IuSigConId 

id-DirectTransf er Information! tem-RANAP-RelocInf 

id-DirectTransf erinf ormationList-RANAP-RelocInf 

id-RAB-Contextltem-RANAP-RelocInf 

id-RAB-ContextList-RANAP-RelocInf 

id-RAB-ContextFailedtoTransferltem 

id-RAB-ContextFailedtoTransferList 

id-GlobalRNC-ID 

id-RAB-Releasedltem-IuRelComp 

id-MessageStructure 

id-Alt-RAB-Parameters 

id-Ass-RAB-Parameters 

id-RAB-ModifyList 

id-RAB-Modifyltem 

id-TypeOfError 

id-BroadcastAssistanceDataDecipheringKeys 

id-LocationRelatedDataRequestType 

id-GlobalCN-ID 

id-Las tKnownService Area 

id-SRB-TrCH-Mapping 

id-VerticalAccuracyCode 

id-Re sponseTime 

id-PositioningPriority 

id-Client Type 



INTEGER : 


:= 68 


INTEGER : 


:= 69 


INTEGER : 


:= 70 


INTEGER ; 


:= 71 


INTEGER : 


:= 72 


INTEGER ; 


:= 75 


INTEGER ; 


:= 76 


INTEGER ; 


:= 77 


INTEGER ; 


:= 78 


INTEGER : 


:= 79 


INTEGER : 


:= 80 


INTEGER : 


:= 81 


INTEGER : 


:= 82 


INTEGER ; 


:= 83 


INTEGER ; 


:= 84 


INTEGER ; 


:= 85 


INTEGER ; 


:= 86 


INTEGER ; 


:= 87 


INTEGER ; 


:= 88 


INTEGER ; 


:= 89 


INTEGER ; 


:= 90 


INTEGER ; 


:= 91 


INTEGER ; 


:= 92 


INTEGER : 


:= 93 


INTEGER : 


:= 94 


INTEGER ; 


:= 95 


INTEGER ; 


:= 96 


INTEGER ; 


:= 97 


INTEGER ; 


:= 98 


INTEGER ; 


:= 111 


INTEGER ; 


:= 112 


INTEGER ; 


:= 113 


INTEGER : 


:= 114 



9.3.7 Container Definitions 



************************************************************** 

— Container definitions 

************************************************************** 

RANAP-Containers { 

itu-t (0) identif ied-organization (4) etsi (0) mobileDomain (0) 

umts-Access (20) modules (3) ranap (0) versionl (1) ranap-Containers (5) } 

DEFINITIONS AUTOMATIC TAGS ;;= 

BEGIN 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



196 



ETSI TS 125 413 V4.10.0 (2003-09) 



************************************************************** 

— IE parameter types from other modules . 

************************************************************** 

IMPORTS 

Criticality, 

Presence, 

PrivatelE-ID, 

ProtocolExtensionID, 

ProtocolIE-ID 
FROM RANAP-CommonDataTypes 

maxPrivatelEs, 
maxProtocolExt ens ions, 
maxProtocolIEs 
FROM RANAP-Constants; 

************************************************************** 

— Class Definition for Protocol lEs 

************************************************************** 



RANAP-PROTOCOL-IES 

&id 

Scriticality 

SValue, 

Spresence 
} 
WITH SYNTAX { 

ID 

CRITICALITY 

TYPE 

PRESENCE 



: := CLASS { 
ProtocolIE-ID 

Criticality, 

Presence 



&id 



Scriticality 

&Value 

Spresence 



UNIQUE, 



************************************************************** 



— Class Definition for Protocol lEs 



************************************************************** 



RANAP-PROTOCOL-IES-PAIR ::= CLASS ( 
&id ProtocolIE-ID 

&f irstCriticality Criticality, 
SFirstValue, 

SsecondCriticality Criticality, 
SSecondValue, 
Spresence Presence 



UNIQUE, 



WITH SYNTAX { 
ID 



Sid 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



197 



ETSI TS 125 413 V4.10.0 (2003-09) 



FIRST CRITICALITY & f irstCriticality 

FIRST TYPE SFirstValue 
SECOND CRITICALITY SsecondCriticality 

SECOND TYPE SSecondValue 

PRESENCE Spresence 



************************************************************** 



— Class Definition for Protocol Extensions 

************************************************************** 



RANAP-PROTOCOL-EXTENSION 



CLASS { 



&id 

Scriticality 
SExtension, 
Spresence 

} 

WITH SYNTAX { 
ID 

CRITICALITY 
EXTENSION 
PRESENCE 



ProtocolExtensionID 
Criticality , 

Presence 



Sid 

&criticality 
SExtension 

Spresence 



UNIQUE, 



************************************************************** 



Class Definition for Private lEs 



************************************************************** 



RANAP-PRIVATE-IES 
Sid 

Scriticality 
SValue, 
Spresence 



:= CLASS { 
PrivatelE-ID, 

Criticality, 

Presence 



WITH SYNTAX { 

ID 

CRITICALITY 

TYPE 

PRESENCE 
1 



Sid 

Scriticality 
SValue 
Spresence 



************************************************************** 

— Container for Protocol lEs 

************************************************************** 

ProtocolIE-Container (RANAP-PROTOCOL-IES : lEsSetParam} ::= 
SEQUENCE (SIZE ( . .maxProtocolIEs ) ) OF 
ProtocolIE-Field ( ( lEsSetParam} } 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 198 ETSI TS 125 413 V4.10.0 (2003-09) 

ProtocolIE-Field { RANAP-PROTOCOL-IES : lEsSetParam} ::= SEQUENCE { 

id RANAP-PROTOCOL-IES. &id ( ( lEsSetParam} ) , 

criticality RANAP-PROTOCOL-IES . Scriticality ( (lEsSetParam} (@id} ) , 

value RANAP-PROTOCOL-IES. SValue (( lEsSetParam} ( @id} ) 
} 

************************************************************** 

— Container for Protocol IE Pairs 

************************************************************** 

ProtocolIE-ContainerPair ( RANAP-PROTOCOL-IES-PAIR : lEsSetParam} ;; = 
SEQUENCE (SIZE ( . .maxProtocolIEs ) ) OF 
ProtocolIE-FieldPair { {lEsSetParam} } 

ProtocolIE-FieldPair (RANAP-PROTOCOL-IES-PAIR : lEsSetParam} ::= SEQUENCE { 

id RANAP-PROTOCOL-IES-PAIR. &id ((lEsSetParam}), 

firstCriticality RANAP-PROTOCOL-IES-PAIR. SfirstCriticality ( {lEsSetParam} (@id} ) , 

firstValue RANAP-PROTOCOL-IES-PAIR. SFirstValue ( ( lEsSetParam} {(aid} ) , 

secondCriticality RANAP-PROTOCOL-IES-PAIR. SsecondCriticality ( {lEsSetParam} {@id} ) , 

secondValue RANAP-PROTOCOL-IES-PAIR. SSecondValue ( {lEsSetParam} {@id} ) 

} 

************************************************************** 

— Container Lists for Protocol IE Containers 

************************************************************** 

ProtocolIE-ContainerList {INTEGER : lowerBound, INTEGER : upperBound, RANAP-PROTOCOL-IES : lEsSetParam} ;;= 
SEQUENCE (SIZE ( lowerBound .. upperBound) ) OF 
ProtocolIE-Container { {lEsSetParam} } 

ProtocolIE-ContainerPairList {INTEGER : lowerBound, INTEGER : upperBound, RANAP-PROTOCOL-IES-PAIR : lEsSetParam} ::= 
SEQUENCE (SIZE ( lowerBound .. upperBound) ) OF 
ProtocolIE-ContainerPair { {lEsSetParam} } 

************************************************************** 

— Container for Protocol Extensions 

************************************************************** 

ProtocolExtensionContainer { RANAP-PROTOCOL-EXTENSION : ExtensionSetParam} :: = 
SEQUENCE (SIZE ( 1 . .maxProtocolExtensions ) ) OF 
ProtocolExtensionField { {ExtensionSetParam} } 

ProtocolExtensionField {RANAP-PROTOCOL-EXTENSION : ExtensionSetParam} ::= SEQUENCE { 

id RANAP-PROTOCOL-EXTENSION. Sid ({ExtensionSetParam}), 

criticality RANAP-PROTOCOL-EXTENSION. Scriticality ( {ExtensionSetParam} {(aid} ) , 

extensionValue RANAP-PROTOCOL-EXTENSION. SExtension ( {ExtensionSetParam} {(aid} ) 

} 

£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



199 



ETSI TS 125 413 V4.10.0 (2003-09) 



************************************************************** 

— Container for Private lEs 

************************************************************** 

PrivatelE-Container { RANAP-PRIVATE-IES : lEsSetParam } ::= 
SEQUENCE (SIZE (1.. maxPrivatelEs ) ) OF 
PrivatelE-Field { { lEsSetParam} } 

PrivatelE-Field (RANAP-PRIVATE-IES : lEsSetParam} ::= SEQUENCE { 

id RANAP-PRIVATE-IES. &id ((lEsSetParam}), 

criticality RANAP-PRIVATE-IES . Scriticality (( lEsSetParam} ( @id} ) 

value RANAP-PRIVATE-IES. SValue (( lEsSetParam} ( @id} ) 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 200 ETSI TS 125 413 V4.10.0 (2003-09) 



9.4 Message Transfer Syntax 



RANAP shall use the ASN.l Basic Packed Encoding Rules (BASIC-PER) Aligned Variant as transfer syntax as 
specified in ref. [13]. 

The following encoding rules apply in addition to what has been specified in X.691 [13]: 

When a bitstring value is placed in a bit-field as specified in 15.6 to 15. 1 1 in [13], the leading bit of the bitstring value 
shall be placed in the leading bit of the bit-field, and the trailing bit of the bitstring value shall be placed in the trailing 
bit of the bit-field. 

NOTE - When using the "bstring" notation, the leading bit of the bitstring value is on the left, and the trailing bit of the 
bitstring value is on the right. The term 'leading bit' is to be interpreted as equal to the term 'first bit' defined in [14]. 

9.5 Timers 

TRELOCprep 

Specifies the maximum time for Relocation Preparation procedure in the source RNC. 

TRELOCoverall 

- Specifies the maximum time for the protection of overall Relocation procedure in the source RNC. 

TreLOC alloc 

Specifies the maximum time for Relocation Resource Allocation procedure in the CN. 

TRELOCcomplete 

Specifies the maximum time for waiting the relocation completion in the CN. 

T RABAssgt 

Specifies the maximum time in the CN for the whole RAB Assignment procedure. 

Tqueuing 

Specifies the maximum time in the RNC for queuing of the request of RAB establishment or modification. 

TDATAfwd 

Specifies the maximum time for GTP-PDU forwarding at the source RNC during relocation of SRNS. 

Tigoc 

While this timer is running, all OVERLOAD messages or signalling point congested information received at the 
CN are ignored. 

TigOR 

While this timer is running, all OVERLOAD messages or signalling point congested information received at the 
RNC are ignored. 

TjnTC 

While this timer is running, the CN is not allowed to increase traffic. 

TinTR 

While this timer is running, the RNC is not allowed to increase traffic. 

TRafC 

Specifies the maximum time for Reset procedure in the RNC. 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



201 



ETSI TS 125 413 V4.10.0 (2003-09) 



Specifies a guard period in the RNC before sending a RESET ACKNOWLEDGE message. 

TroTR 

Specifies the maximum time for Reset procedure in the CN. 

TRatR 

Specifies a guard period in the CN before sending a RESET ACKNOWLEDGE message. 

10 Handling of Unknown, Unforeseen and Erroneous 
Protocol Data 

10.1 General 

Protocol Error cases can be divided into three classes: 

Transfer Syntax Error. 

Abstract Syntax Error. 

Logical Error. 
Protocol errors can occur in the following functions within a receiving node: 



RANAP 

functional 

entity 



>- 



A 



ASN.l Decoding 



> 



Logical Errors 
Abstract Syntax Errors 



Transfer Syntax Errors 



/N 



Figure 39: Protocol Errors in RANAP. 

The information stated in subclauses 10.2, 10.3 and 10.4, to be included in the message used when reporting an error, is 
what at minimum shall be included. Other optional information elements within the message may also be included, if 
available. This is also valid for the case when the reporting is done with a response message. The latter is an exception 
to what is stated in subclause 4. 1 . 



10.2 Transfer Syntax Error 



A Transfer Syntax Error occurs when the receiver is not able to decode the received physical message. Transfer syntax 
errors are always detected in the process of ASN. 1 decoding. If a Transfer Syntax Error occurs, the receiver should 
initiate Error Indication procedure with appropriate cause value for the Transfer Syntax protocol error. 

Examples for Transfer Syntax Errors are: 

Violation of value ranges in ASN. 1 definition of messages, e.g.: If an IE has a defined value range of to 10 
(ASN.l: INTEGER (0..10)), and 12 will be received, then this will be treated as a transfer syntax error. 

Violation in list element constraints, e.g.: If a list is defined as containing 1 to 10 elements, and 12 elements will 
be received, than this case will be handled as a transfer syntax error. 

Missing mandatory elements in ASN. 1 SEQUENCE definitions (as sent by the originator of the message). 



£75/ 



3GPP TS 25.41 3 version 4.1 0.0 Release 4 202 ETSI TS 1 25 41 3 V4.1 0.0 (2003-09) 

Wrong order of elements in ASN. 1 SEQUENCE definitions (as sent by the originator of the message). 



1 0.3 Abstract Syntax Error 

10.3.1 General 

An Abstract Syntax Error occurs when the receiving functional RANAP entity: 

1. receives lEs or IE groups that cannot be understood (unknown IE ID); 

2. receives lEs for which the logical range is violated (e.g.: ASN.l definition: to 15, the logical range is to 10 
(values 11 to 15 are undefined), and 12 will be received; this case will be handled as an abstract syntax error using 
criticality information sent by the originator of the message); 

3. does not receive lEs or IE groups but according to the specified presence of the concerning object, the lEs or IE 
groups should have been present in the received message. 

4. receives lEs or IE groups that are defined to be part of that message in wrong order or with too many occurrences of 
the same IE or IE group; 

5. receives lEs or IE groups but according to the conditional presence of the concerning object and the specified 
condition, the lEs or IE groups should not have been present in the received message. 

Cases 1 and 2 (not comprehended IE/IE group) are handled based on received Criticality information. Case 3 (missing 
IE/IE group) is handled based on Criticality information and Presence information for the missing IE/IE group specified 
in the version of the specification used by the receiver. Case 4 (lEs or IE groups in wrong order or with too many 
occurrences) and Case 5 (erroneously present conditional lEs or IE groups) result in rejecting the procedure. 

If an Abstract Syntax Error occurs, the receiver shall read the remaining message and shall then for each detected 
Abstract Syntax Error that belong to cases 1 -3 act according to the Criticality Information and Presence Information for 
the IE/IE group due to which Abstract Syntax Error occurred in accordance with subclauses 10.3.4 and 10.3.5. The 
handling of cases 4 and 5 is specified in subclause 10.3.6. 

10.3.2 Criticality Information 

In the RANAP messages there is criticality information set for individual lEs and/or IE groups. This criticality 
information instructs the receiver how to act when receiving an IE or an IE group that is not comprehended, i.e. the 
entire item (IE or IE group) which is not (fully or partially) comprehended shall be treated in accordance with its own 
criticality information as specified in subclause 10.3.4. 

In addition, the criticality information is used in case of the missing IE/IE group abstract syntax error (see subclause 
10.3.5). 

The receiving node shall take different actions depending on the value of the Criticality Information. The three possible 
values of the Criticality Information for an IE/IE group are: 

Reject IE. 

Ignore IE and Notify Sender. 

Ignore IE. 

The following rules restrict when a receiving entity may consider an IE, an IE group, or an EP not comprehended (not 
implemented), and when action based on criticality information is applicable: 

1 . IE or IE group: When one new or modified IE or IE group is implemented for one EP from a standard version, 
then other new or modified lEs or IE groups specified for that EP in that standard version shall be considered 
comprehended by a receiving entity (some may still remain unsupported). 

Note that this restriction is not applicable to a sending entity for constructing messages. 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 203 ETSI TS 125 413 V4.10.0 (2003-09) 

2. EP: The comprehension of different EPs within a standard version or between different standard versions is not 
mandated. Any EP that is not supported may be considered not comprehended, even if another EP from that 
standard version is comprehended, and action based on criticaHty shall be applied. 

10.3.3 Presence Information 

For many lEs/IE groups which are optional according to the ASN. 1 transfer syntax, RANAP specifies separately if the 
presence of these lEs/IE groups is optional or mandatory with respect to RNS application by means of the presence field 
of the concerning object of class RANAP-PROTOCOL-IES, RANAP-PROTOCOL-IES-PAIR, RANAP-PROTOCOL- 
EXTENSION or RANAP-PRIVATE-IES. 

The presence field of the indicated classes supports three values: 

1. Optional; 

2. Conditional; 

3. Mandatory. 

If an IE/IE group is not included in a received message and the presence of the IE/IE group is mandatory or the 
presence is conditional and the condition is true according to the version of the specification used by the receiver, an 
abstract syntax error occurs due to a missing IE/IE group. 

If an IE/IE group is included in a received message and the presence of the IE/IE group is conditional and the condition 
is false according to the version of the specification used by the receiver, an abstract syntax error occurs due to this 
erroneously present conditional IE/IE group. 

1 0.3.4 Not comprehended IE/IE group 
10.3.4.1 Procedure Code 

The receiving node shall treat the different types of received criticality information of the Procedure Code IE according 
to the following: 

Reject IE: 

If a message is received with a Procedure Code IE marked with "Reject IE" which the receiving node does not 
comprehend, the receiving node shall reject the procedure using the Error Indication procedure. 

Ignore IE and Notify Sender: 

If a message is received with a Procedure Code IE marked with "Ignore IE and Notify Sender" which the 
receiving node does not comprehend, the receiving node shall ignore the procedure and initiate the Error 
Indication procedure. 

Ignore IE: 

If a message is received with a Procedure Code IE marked with "Ignore IE" which the receiving node does not 
comprehend, the receiving node shall ignore the procedure. 

When using the Error Indication procedure to reject a procedure or to report an ignored procedure it shall include the 
Procedure Code IE, the Triggering Message IE, and the Procedure Criticality IE in the Criticality Diagnostics IE. 

1 0.3.4.1 A Type of Message 

When the receiving node cannot decode the Type of Message IE, the Error Indication procedure shall be initiated with 
an appropriate cause value. 

1 0.3.4.2 lEs other than the Procedure Code and Type of Message 

The receiving node shall treat the different types of received criticality information of an lEs/IE group other than the 
Procedure Code IE according to the following: 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 204 ETSI TS 125 413 V4.10.0 (2003-09) 

Reject IE: 

If a message initiating a procedure is received containing one or more lEs/IE group marked with "Reject IE" 
which the receiving node does not comprehend; none of the functional requests of the message shall be executed. 
The receiving node shall reject the procedure and report the rejection of one or more lEs/IE group using the 
message normally used to report unsuccessful outcome of the procedure. In case the information received in the 
initiating message was insufficient to determine a value for all lEs that are required to be present in the message 
used to report the unsuccessful outcome of the procedure, the receiving node shall instead terminate the 
procedure and initiate the Error Indication procedure. 

If a message initiating a procedure that does not have a message to report unsuccessful outcome is received 
containing one or more lEs/IE groups marked with "Reject IE" which the receiving node does not comprehend, 
the receiving node shall terminate the procedure and initiate the Error Indication procedure. 

If a response message is received containing one or more lEs marked with "Reject IE", that the receiving node 
does not comprehend, the receiving node shall consider the procedure as unsuccessfully terminated and initiate 
local error handling. 

Ignore IE and Notify Sender: 

If a message initiating a procedure is received containing one or more lEs/IE groups marked with "Ignore IE and 
Notify Sender" which the receiving node does not comprehend, the receiving node shall ignore the content of the 
not comprehended lEs/IE groups, continue with the procedure as if the not comprehended lEs/IE groups were 
not received (except for the reporting) using the understood lEs/IE groups, and report in the response message of 
the procedure that one or more lEs/IE groups have been ignored. In case the information received in the 
initiating message was insufficient to determine a value for all lEs that are required to be present in the response 
message, the receiving node shall instead terminate the procedure and initiate the Error Indication procedure. 

if a message initiating a procedure that does not have a message to report the outcome of the procedure is 
received containing one or more lEs/IE groups marked with "Ignore IE and Notify Sender" which the receiving 
node does not comprehend, the receiving node shall ignore the content of the not comprehended lEs/IE groups, 
continue with the procedure as if the not comprehended lEs/IE groups were not received (except for the 
reporting) using the understood lEs/IE groups, and initiate the Error Indication procedure to report that one or 
more lEs/IE groups have been ignored. 

If a response message is received containing one or more lEs/IE groups marked with "Ignore IE and Notify 
Sender" which the receiving node does not comprehend, the receiving node shall ignore the content of the not 
comprehended lEs/IE groups, continue with the procedure as if the not comprehended lEs/IE groups were not 
received (except for the reporting) using the understood lEs/IE groups and initiate the Error Indication 
procedure. 

Ignore IE: 

If a message initiating a procedure is received containing one or more lEs/IE groups marked with "Ignore IE" 
which the receiving node does not comprehend, the receiving node shall ignore the content of the not 
comprehended lEs/IE groups and continue with the procedure as if the not comprehended lEs/IE groups were 
not received using the understood lEs/IE groups. 

If a response message is received containing one or more lEs/IE groups marked with "Ignore IE" which the 
receiving node does not comprehend, the receiving node shall ignore the content of the not comprehended lEs/IE 
groups and continue with the procedure as if the not comprehended lEs/IE groups were not received using the 
understood lEs/IE groups. 

When reporting not comprehended lEs/IE groups marked with "Reject IE" or "Ignore IE and Notify Sender" using a 
response message defined for the procedure, the Information Element Criticality Diagnostics IE shall be included in the 
Criticality Diagnostics IE for each reported IE/IE group. In the Information Element Criticality Diagnostics lEthe 
Repetition Number IE shall be included and in addition, if the not comprehended IE/IE group is not at message 
hierarchy level 1 (top level; see annex A2) also the Message Structure IE shall be included. 

When reporting not comprehended lEs/IE groups marked with "Reject IE" or "Ignore IE and Notify Sender" using the 
Error Indication procedure, the Procedure Code IE, the Triggering Message IE, Procedure Criticality IE, and the 
Information Element Criticality Diagnostics IE shall be included in the Criticality Diagnostics IE for each reported 
IE/IE group. In the Information Element Criticality Diagnostics lEthe Repetition Number IE shall be included and in 



£75/ 



3GPP TS 25.41 3 version 4.1 0.0 Release 4 205 ETSI TS 1 25 41 3 V4.1 0.0 (2003-09) 

addition, if the not comprehended IE/IE group is not at message hierarchy level 1 (top level; see annex A2) also the 
Message Structure IE shall be included. 

1 0.3.5 Missing IE or IE group 

The receiving node shall treat the missing IE/IE group according to the criticality information for the missing IE/IE 
group in the received message specified in the version of this specification used by the receiver: 

Reject IE: 

if a received message initiating a procedure is missing one or more lEs/IE groups with specified criticality 
"Reject IE"; none of the functional requests of the message shall be executed. The receiving node shall reject 
the procedure and report the missing lEs/IE groups using the message normally used to report unsuccessful 
outcome of the procedure. In case the information received in the initiating message was insufficient to 
determine a value for all lEs that are required to be present in the message used to report the unsuccessful 
outcome of the procedure, the receiving node shall instead terminate the procedure and initiate the Error 
Indication procedure. 

if a received message initiating a procedure that does not have a message to report unsuccessful outcome is 
missing one or more lEs/IE groups with specified criticality "Reject IE", the receiving node shall terminate the 
procedure and initiate the Error Indication procedure. 

if a received response message is missing one or more lEs/IE groups with specified criticality "Reject IE, the 
receiving node shall consider the procedure as unsuccessfully terminated and initiate local error handling. 

Ignore IE and Notify Sender: 

if a received message initiating a procedure is missing one or more lEs/IE groups with specified criticality 
"Ignore IE and Notify Sender", the receiving node shall ignore that those lEs are missing and continue with the 
procedure based on the other lEs/IE groups present in the message and report in the response message of the 
procedure that one or more lEs/IE groups were missing. In case the information received in the initiating 
message was insufficient to determine a value for all lEs that are required to be present in the response message, 
the receiving node shall instead terminate the procedure and initiate the Error Indication procedure. 

if a received message initiating a procedure that does not have a message to report the outcome of the procedure 
is missing one or more lEs/IE groups with specified criticality "Ignore IE and Notify Sender", the receiving node 
shall ignore that those lEs are missing and continue with the procedure based on the other lEs/IE groups present 
in the message and initiate the Error Indication procedure to report that one or more lEs/IE groups were missing. 

if a received response message is missing one or more lEs/IE groups with specified criticality "Ignore IE and 
Notify Sender", the receiving node shall ignore that those lEs are missing and continue with the procedure based 
on the other lEs/IE groups present in the message and initiate the Error Indication procedure to report that one or 
more lEs/IE groups were missing. 

Ignore IE: 

if a received message initiating a procedure is missing one or more lEs/IE groups with specified criticality 
"Ignore IE" , the receiving node shall ignore that those lEs are missing and continue with the procedure based on 
the other lEs/IE groups present in the message. 

if a received response message is missing one or more lEs/IE groups with specified criticality "Ignore IE", the 
receiving node shall ignore that those lEs/IE groups are missing and continue with the procedure based on the 
other lEs/IE groups present in the message. 

When reporting missing lEs/IE groups with specified criticality "Reject IE" or "Ignore IE and Notify Sender" using a 
response message defined for the procedure, the Information Element Criticality Diagnostics IE shall be included in the 
Criticality Diagnostics IE for each reported IE/IE group. In the Information Element Criticality Diagnostics IE the 
Repetition Number IE shall be included and in addition, if the missing IE/IE group is not at message hierarchy level 1 
(top level; see annex A2) also the Message Structure IE shall be included. 

When reporting missing lEs/IE groups with specified criticality "Reject IE" or "Ignore IE and Notify Sender" using the 
Error Indication procedure, the Procedure Code IE, the Triggering Message IE, Procedure Criticality IE, and the 
Information Element Criticality Diagnostics IE shall be included in the Criticality Diagnostics IE for each reported 
IE/IE group. In the Information Element Criticality Diagnostics IE the Repetition Number IE shall be included and in 



£75/ 



3GPP TS 25.41 3 version 4.1 0.0 Release 4 206 ETSI TS 1 25 41 3 V4.1 0.0 (2003-09) 

addition, if the missing IE/IE group is not at message hierarchy level 1 (top level; see annex A2) also the Message 
Structure IE shall be included. 

1 0.3.6 lEs or IE groups received in wrong order or witin too many 
occurrences or erroneously present 

If a message with lEs or IE groups in wrong order or with too many occurrences is received or if lEs or IE groups with 
a conditional presence are present when the condition is not met (i.e. erroneously present), the receiving node shall 
behave according to the following: 

If a message initiating a procedure is received containing lEs or IE groups in wrong order or with too many 
occurrences or erroneously present, none of the functional requests of the message shall be executed. The 
receiving node shall reject the procedure and report the cause value "Abstract Syntax Error (Falsely Constructed 
Message)" using the message normally used to report unsuccessful outcome of the procedure. In case the 
information received in the initiating message was insufficient to determine a value for all lEs that are required 
to be present in the message used to report the unsuccessful outcome of the procedure, the receiving node shall 
instead terminate the procedure and initiate the Error Indication procedure. 

If a message initiating a procedure that does not have a message to report unsuccessful outcome is received 
containing lEs or IE groups in wrong order or with too many occurrences or erroneously present, the receiving 
node shall terminate the procedure and initiate the Error Indication procedure, and use cause value "Abstract 
Syntax Error (Falsely Constructed Message)". 

If a response message is received containing lEs or IE groups in wrong order or with too many occurrences or 
erroneously present, the receiving node shall consider the procedure as unsuccessfully terminated and initiate 
local error handling. 

When determining the correct order only the lEs specified in the specification version used by the receiver shall be 
considered. 



10.4 Logical Error 



Logical error situations occur when a message is comprehended correctly, but the information contained within the 
message is not valid (i.e. semantic error), or describes a procedure which is not compatible with the state of the receiver. 
In these conditions, the following behaviour shall be performed (unless otherwise specified) as defined by the class of 
the elementary procedure, irrespective of the criticality information of the lEs/IE groups containing the erroneous 
values. 

Class 1: 



Where the logical error occurs in a request message of a class 1 procedure, and the procedure has a message to report 
this unsuccessful outcome, this message shall be sent with an appropriate cause value. Typical cause values are: 

Semantic Error. 

Message not compatible with receiver state. 

Where the logical error is contained in a request message of a class 1 procedure, and the procedure does not have a 
message to report this unsuccessful outcome, the procedure shall be terminated and the Error Indication procedure shall 
be initiated with an appropriate cause value. The Procedure Code IE and the Triggering Message IE within the 
Criticality Diagnostics IE shall then be included in order to identify the message containing the logical error. 

Where the logical error exists in a response message of a class 1 procedure, the procedure shall be considered as 
unsuccessfully terminated and local error handling shall be initiated. 

Class 2: 

Where the logical error occurs in a message of a class 2 procedure, the procedure shall be terminated and the Error 
Indication procedure shall be initiated with an appropriate cause value. The Procedure Code IE and the Triggering 
Message IE within the Criticality Diagnostics IE shall then be included in order to identify the message containing the 
logical error. 



£75/ 



3GPP TS 25.41 3 version 4.1 0.0 Release 4 207 ETSI TS 1 25 41 3 V4.1 0.0 (2003-09) 

Class 3: 

Where the logical error occurs in a request message of a class 3 procedure, and the procedure has a message to report 
this unsuccessful outcome, this message shall be sent with an appropriate cause value. Typical cause values are: 

Semantic Error. 

Message not compatible with receiver state. 

Where the logical error is contained in a request message of a class 3 procedure, and the procedure does not have a 
message to report this unsuccessful outcome, the procedure shall be terminated and the Error Indication procedure shall 
be initiated with an appropriate cause value. The Procedure Code IE and the Triggering Message IE within the 
Criticality Diagnostics IE shall then be included in order to identify the message containing the logical error. 

Where the logical error exists in a response message of a class 3 procedure, the procedure shall be considered as 
unsuccessfully terminated and local error handling shall be initiated. 



10.5 Exceptions 



The error handling for all the cases described hereafter shall take precedence over any other error handling described in 
the other subclauses of clause 10. 

If any type of error (Transfer Syntax Error, Abstract Syntax Error or Logical Error) is detected in the ERROR 
INDICATION message, it shall not trigger the Error Indication procedure in the receiving Node but local error 
handling. 

In case a response message or Error Indication message needs to be returned, but the information necessary to 
determine the receiver of that message is missing, the procedure shall be considered as unsuccessfully terminated 
and local error handling shall be initiated. 

If an error that terminates a procedure occurs, the returned cause value shall reflect the error that caused the 
termination of the procedure even if one or more abstract syntax errors with criticality "ignore and notify" have 
earlier occurred within the same procedure. 



1 1 Special Procedures for RNC to RNC Communication 

11.1 General 

This subclause specifies special procedures that are used for RNC to RNC communication, and use other transport 
means than the RANAP procedures specified in clause 8. 

1 1 .2 RANAP Relocation Information 
11.2.1 General 

The purpose of the RANAP Relocation Information procedure is to handle the RANAP related information that is 
carried transparently during relocation from source RNC to target RNC by RNSAP via lur Interface. 



1 1 .2.2 Operation 



When during relocation it becomes necessary in the source RNC to generate RANAP information for transfer to the 
relocation target, the RNC shall form a RANAP RELOCATION INFORMATION message. The message shall be 
encoded according to the encoding rules specified for RANAP in the similar manner as for the normal RANAP 
messages. The outcome of the encoding will be an octet string, which shall not be sent to the CN via the lu Interface, 
but it shall be given to the appropriate local process for transparent transfer to the target RNC. 

When the RANAP process in the target RNC receives an octet string containing RANAP RELOCATION 
INFORMATION message that had been transparently transferred from the source RNC, it shall decode it according to 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 208 ETSI TS 125 413 V4.10.0 (2003-09) 

the encoding rules specified for RANAP. This process is similar to receiving any normal RANAP message. The 
decoded information shall be passed to the appropriate processes in the RNC. 

The RANAP RELOCATION INFORMATION message may contain the Direct Transfer Information IE and the RAB 
Contexts IE. If present, the Direct Transfer Information IE shall contain the NAS-PDU IE, the SAPI IE and the CN 
Domain Indicator IE. If present, the RAB Contexts IE shall contain for each addressed RAB the RAB ID IE and, if 
available, the DL GTP-PDU Sequence Number IE, the UL GTP-PDU Sequence Number IE, the DL N-PDU Sequence 
Number IE or the UL N-PDU Sequence Number IE. 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



209 



ETSI TS 125 413 V4.10.0 (2003-09) 



Annex A (informative): 
RANAP guidelines 

A.1 Rules for building RANAP messages 

A.1 .1 Rules for RANAP messages that shall contain the CN Domain 
Indicator IE 

Based on the principles described in [3], following rules can be deduced: 

1) Any RANAP message initiating a connection oriented signalling connection shall contain the CN Domain 
Indicator IE. For the time being, two such RANAP messages are known: INITIAL UE MESSAGE message 
and RELOCATION REQUEST message. 

2) Any RANAP message belonging to class 1 procedures that uses connectionless signalling shall contain the 
CN Domain Indicator IE. 

3) Following RANAP message belonging to class 2 procedures that uses connectionless signalling shall contain 
the CN Domain Indicator IE: PAGING message and ERROR INDICATION message, the OVERLOAD 
message in DL direction (see chapter 8.25.3.1) may contain the CN Domain Indicator IE. 

A.2 Guidelines for Usage of the Criticality Diagnostics IE 
A.2.1 EXAMPLE MESSAGE Layout 

Assume the following message format: 



IE/Group Name 


Presence 


Range 


IE type 

and 

referenc 

e 


Semantics 
description 


Criticality 


Assigned 
Criticality 


Message Type 


M 








YES 


reject 


A 


M 








YES 


reject 


B 


M 








YES 


reject 


>E 




1..<maxE> 






EACH 


ignore 


»F 




1..<maxF> 






- 




»>G 




0..3, ... 






EACH 


ignore 


»H 




1..<maxH> 






EACH 


ignore 


»>G 




0..3, ... 






EACH 


ignore and 
notify 


»G 


M 








YES 


reject 


»J 




1..<maxJ> 






- 




»>G 




0..3, ... 






EACH 


reject 


C 


M 








YES 


reject 


>K 




1..<maxK> 






EACH 


ignore and 
notify 


»L 




1..<maxL> 






- 




»>M 











- 




D 


M 








YES 


reject 

















Note 1 . The lEs F, J, and L do not have assigned criticality. The lEs F, J, and L are consequently realised as the 

ASN.l type SEQUENCE OF of "ordinary" ASN.l type, e.g. INTEGER. On the other hand, the repeatable 
lEs with assigned criticality are realised as the ASN.l type SEQUENCE OF of an IE object, e.g. 
ProtocolIE-Container. 

For the corresponding ASN.l layout, see subclause A.2.4. 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



210 



ETSI TS 125 413 V4.10.0 (2003-09) 



A.2.2 Example on a Received EXAMPLE MESSAGE 

Assume further more that a received message based on the above tabular format is according to the figure below. 



Level 1 
(top level) 



Level 2 



Level 3 



Level 4 



r. 



B 



H 


-1 


v 












G 


- 


1 





G 



G 



C 



K 



: J 



G 



D 



3... 



G 



G 



Legend: 




l*"' repetition 



,nd 



2 repetition 



rth 



N repetition 



IE based on a protocol container 
; IE being an "ordinary" ASN.l type 



Figure A.1 : Example of content of a received RANAP message based on the EXAMPLE MESSAGE 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



211 



ETSI TS 125 413 V4.10.0 (2003-09) 



A.2.3 Content of Criticality Diagnostics 
A.2.3.1 Example 1 



Level 1 
(top level) 



Level 2 



C 



D 



Included in the 
Message Structure IE. 



Level 3 



Level 4 











"1 


1 


1 












G 

1 


- 






G 

4 


1 


2 










H 


— 1 


V 












G 


— 


1 





Included in the Information Element Criticality Diagnostics IE: 

a) IE ID IE 

b) Repetition Number IE 

Figure A.2: Example of a received RANAP message containing a not comprehended IE 

If there is an error within the instance marked as grey in the IE G in the IE J shown in the figure A.2 above, this will be 
reported within the Information Element Criticality Diagnostics IE within the Criticality Diagnostics IE as follows: 



IE name 


Value 


Comment 


IE Criticality 


reject 


Criticality for IE on the reported level, i.e. level 4. 


IE ID 


id-G 


IE ID from the reported level, i.e. level 4. 


Repetition 
Number 


11 


Repetition number on the reported level, i.e. level 4. 

(Since the IE E (level 2) is the lowest level included in the Message Structure IE this is 

the eleventh occurrence of IE G within the IE E (level 2). 


Type of Error 


not 

underst 

ood 




IVIessage Structure, first repetition 


>IEID 


id-B 


IE ID from level 1. 




IVIessage Structure, second repetition 


>IEID 


id-E 


IE ID from the lowest level above the reported level, i.e. level 2. 


>Repetition 
Number 


3 


Repetition number from the lowest level above the reported level, i.e. level 2. 



Note 2. The IE J on level 3 cannot be included in the Message Structure IE since they have no criticality of their 
own. 

Note 3. The repetition number of the reported IE indicates the number of repetitions of IE G received up to the 
detected erroneous repetition, counting all occurrences of the IE G below the same instance of the 
previous level with assigned criticality (instance 3 of IE E on level 2). 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



212 



ETSI TS 125 413 V4.10.0 (2003-09) 



A.2.3.2 



Example 2 



Level 1 
(top level) 



Level 2 



Included in the 

Message Structure IE. 



Level 3 



: F 



Level 4 











"1 


— 1 


1 












G 


- 






G 


1 











H 


— 1 


V 












G 


— 


1 






Included in the Information Element Criticality Diagnostics IE; 

a) IE ID IE 

b) Repetition Number IE 

Figure A.3: Example of a received RANAP message containing a not comprehended IE 

If there is an error within the second instance (marked as grey) in the sequence (IE L in the tabular format) on level 3 
below IE K in the structure shown in the figure A.3 above, this will be reported within the Information Element 
Criticality Diagnostics IE within the Criticality Diagnostics IE as follows: 



IE name 


Value 


Comment 


IE Criticality 


ignore 

and 

notify 


Criticality for IE on the reported level, i.e. level 2. 


IE ID 


id-K 


IE ID from the reported level, i.e. level 2. 


Repetition 
Number 


3 


Repetition number on the reported level, i.e. level 2. 


Type of Error 


not 

underst 

ood 




IVIessage Structure, first repetition 


>IEID 


id-C 


IE ID from the lowest level above the reported level, i.e. 


level 1 . 



Note 4. The IE L on level 3 cannot be reported individually included in the Message Structure IE since it has no 
criticality of its own. 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



213 



ETSI TS 125 413 V4.10.0 (2003-09) 



A.2.3.3 



Example 3 



Level 1 
(top level) 



Level 2 



Included in the 
Message Structure IE. 



Level 3 




Level 4 



Included in the Information Element Criticality Diagnostics IE: 

a) IE ID IE 

b) Repetition Number IE 



Figure A.4: Example of a received RANAP message containing a not comprehended IE 

If there is an error within the instance marked as grey in the IE G in the IE H shown in the figure A.4 above, this will be 
reported within the Information Element Criticality Diagnostics IE within the Criticality Diagnostics IE as follows: 



IE name 


Value 


Comment 


IE Criticality 


ignore 

and 

notify 


Criticality for IE on the reported level, i.e. level 4. 


IE ID 


id-G 


IE ID from the reported level, i.e. level 4. 


Repetition 
Number 


2 


Repetition number on the reported level, i.e. level 4. 


Type of Error 


not 

underst 

ood 




IVIessage Structure, first repetition 


>IEID 1 id-B 1 IE ID from level 1. 


Message Structure, second repetition 


>IEID 


id-E 


IE ID from level 2. 


>Repetition 
Number 


3 


Repetition number from level 2. 


IVIessage Structure, third repetition 


>IEID 


id-H 


IE ID from the lowest level above the reported level, i.e. level 3. 


>Repetition 
Number 


1 


Repetition number from the lowest level above the reported level, i.e. level 3. 



Note 5. The repetition number of level 4 indicates the number of repetitions of IE G received up to the detected 
erroneous repetition, counted below the same instance of the previous level with assigned criticality 
(instance 1 of IE H on level 3). 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



214 



ETSI TS 125 413 V4.10.0 (2003-09) 



A.2.3.4 



Example 4 



Level 1 
(top level) 



Level 2 



Included in the 

Message Structure IE. 



Level 3 



: F 



Level 4 











"1 


1 


1 












G 

1 


- 






G 

4 


1 


2 










Included in the Information Element Criticality Diagnostics IE: 

a) IE ID IE 

b) Repetition Number IE 

Figure A.5: Example of a received RANAP message containing a not comprehended IE 

If there is an error within the instance marked as grey in the IE G in the IE E shown in the figure A.5 above, this will be 
reported within the Information Element Criticality Diagnostics IE within the Criticality Diagnostics IE as follows: 



IE name 


Value 


Comment 


IE Criticality 


reject 


Criticality for IE on the reported level, i.e. level 3. 


IE ID 


id-G 


IE ID from the reported level, i.e. level 3. 


Repetition 
Number 


5 


Repetition number on the reported level, i.e. level 3. 

(Since the IE E (level 2) is the lowest level included in the Message Structure IE this is 

the fifth occurrence of IE G within the IE E (level 2). 


Type of Error 


not 

underst 

ood 




IVIessage Structure, first repetition 


>IEID 1 id-B 1 IE ID from level 1. 


Message Structure, second repetition 


>IEID 


id-E 


IE ID from the lowest level above the reported level, i.e. level 2. 


>Repetition 
Number 


3 


Repetition number from the lowest level above the reported level, i.e. level 2. 



Note 6. The repetition number of the reported IE indicates the number of repetitions of IE G received up to the 
detected erroneous repetition, counting all occurrences of the IE G below the same instance of the 
previous level with assigned criticality (instance 3 of IE E on level 2). 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



215 



ETSI TS 125 413 V4.10.0 (2003-09) 



A.2.3.5 



Example 5 



Level 1 
(top level) 



Level 2 



Included in the 

Message Structure IE. 



Level 3 



: F 



Level 4 



G 



G 



T 




H 


— 1 


V 












G 


— 


1 





Included in the Information Element Criticality Diagnostics IE: 

a) IE ID IE 

b) Repetition Number IE 

Figure A.6: Example of a received RANAP message with a missing IE 

If the instance marked as grey in the IE G in the IE E shown in the figure A.6 above, is missing this will be reported 
within the Information Element Criticality Diagnostics IE within the Criticality Diagnostics IE as follows: 



IE name 


Value 


Comment 


IE Criticality 


reject 


Criticality for IE on the reported level, i.e. level 3. 


IE ID 


id-G 


IE ID from the reported level, i.e. level 3. 


Repetition 
Number 


4 


Repetition number up to the missing IE on the reported level, i.e. level 3. 

(Since the IE E (level 2) is the lowest level included in the Message Structure IE there 

have been four occurrences of IE G within the IE E (level 2) up to the missing 

occurrence. 


Type of Error 


missing 




IVIessage Structure, first repetition 


>IEID 1 id-B 1 IE ID from level 1. 


Message Structure, second repetition 


>IEID 


id-E 


IE ID from the lowest level above the reported level, i.e. level 2. 


>Repetition 
Number 


3 


Repetition number from the lowest level above the reported level, i.e. level 2. 



Note 7. The repetition number of the reported IE indicates the number of repetitions of IE G received up to but 

not including the missing occurrence, counting all occurrences of the IE G below the same instance of the 
previous level with assigned criticality (instance 3 of IE E on level 2). 



£75/ 



3GPP TS 25.41 3 version 4.1 0.0 Release 4 216 ETSI TS 1 25 41 3 V4.1 0.0 (2003-09) 

A.2.4 ASN.1 of EXAMPLE MESSAGE 

ExampleMessage ::= SEQUENCE { 

ProtocolIEs ProtocolIE-Container ( (ExampleMessage-IEs } } , 

ProtocolExtensions ProtocolExtensionContainer ( (ExampleMessage-Extensions } } OPTIONAL, 



ExampleMessage-IEs RANAP-PROTOCOL-IES ::= { 

{ ID id-A CRITICALITY reject TYPE A PRESENCE mandatory} | 

{ ID id-B CRITICALITY reject TYPE B PRESENCE mandatory} | 

{ ID id-C CRITICALITY reject TYPE C PRESENCE mandatory} | 

{ ID id-D CRITICALITY reject TYPE D PRESENCE mandatory} , 



B : := SEQUENCE { 

e E-List, 

IE-Extensions ProtocolExtensionContainer { {B-ExtlEs} } OPTIONAL, 



B-ExtlEs RANAP-PROTOCOL-EXTENSION ::= { 



E-List ::= SEQUENCE (SIZE (L.maxE)) OF ProtocolIE-Container { {E-IEs} 

E-IEs RANAP-PROTOCOL-IES ::= { 

{ ID id-E CRITICALITY ignore TYPE E PRESENCE mandatory }, 



E : := SEQUENCE { 

f F-List, 

h H-List, 

g G-Listl, 

j J-List, 

IE-Extensions ProtocolExtensionContainer { {E-ExtlEs} } OPTIONAL, 



E-ExtlEs RANAP-PROTOCOL-EXTENSION ::= { 



F-List ::= SEQUENCE (SIZE (L.maxF)) OF F 

F : := SEQUENCE { 

g G-List2 OPTIONAL, 

IE-Extensions ProtocolExtensionContainer { {F-ExtlEs} } OPTIONAL, 



F-ExtlEs RANAP-PROTOCOL-EXTENSION ::= { 



G-List2 ::= SEQUENCE (SIZE (1..3, ...)) OF ProtocolIE-Container { {G2-IEs) 

G2-IES RANAP-PROTOCOL-IES ::= { 

{ ID id-G CRITICALITY ignore TYPE G PRESENCE mandatory }, 



H-List ::= SEQUENCE (SIZE (L.maxH)) OF ProtocolIE-Container { {H-IEs} } 

H-IEs RANAP-PROTOCOL-IES ::= { 

{ ID id-H CRITICALITY ignore TYPE H PRESENCE mandatory }, 

} 

H : := SEQUENCE { 

g G-List3 OPTIONAL, 

IE-Extensions ProtocolExtensionContainer { {H-ExtlEs} } OPTIONAL, 



£75/ 



3GPP TS 25.41 3 version 4.1 0.0 Release 4 217 ETSI TS 1 25 41 3 V4.1 0.0 (2003-09) 



H-ExtlEs RANAP-PROTOCOL-EXTENSION 



G-List3 ::= SEQUENCE (SIZE (1..3, ...)) OF ProtocolIE-Container { {G3-IEs} } 

G3-IES RANAP-PROTOCOL-IES ::= { 

{ ID id-G CRITICALITY notify TYPE G PRESENCE mandatory }, 

} 

G-Listl ::= ProtocolIE-Container { {Gl-IEs} } 

Gl-IEs RANAP-PROTOCOL-IES ::= { 

{ ID id-G CRITICALITY reject TYPE G PRESENCE mandatory }, 



J-List ::= SEQUENCE (SIZE (L.maxJ)) OF J 

J : := SEQUENCE { 

g G-List4 OPTIONAL, 

iE-Extensions ProtocolExtensionContainer { {J-ExtlEs} } OPTIONAL, 



J-ExtlEs RANAP-PROTOCOL-EXTENSION 



G-List4 ::= SEQUENCE (SIZE (1..3, ...)) OF ProtocolIE-Container { {G4-IEs) 

G4-IES RANAP-PROTOCOL-IES ::= { 

{ ID id-G CRITICALITY reject TYPE G PRESENCE mandatory }, 

) 

C : := SEQUENCE { 

k K-List, 

iE-Extensions ProtocolExtensionContainer { {C-ExtlEs} } OPTIONAL, 

) 

C-ExtlEsA -PROTOCOL-EXTENSION ::= { 

} 

K-List ::= SEQUENCE (SIZE (L.maxK)) OF ProtocolIE-Container { {K-IEs} } 

K-IEs RANAP-PROTOCOL-IES ::= { 

{ ID id-K CRITICALITY notify TYPE K PRESENCE mandatory }, 



K : := SEQUENCE { 

1 L-List, 

iE-Extensions ProtocolExtensionContainer { {K-ExtlEs} } OPTIONAL, 



K-ExtlEs RANAP-PROTOCOL-EXTENSION ::= { 

} 

L-List ::= SEQUENCE (SIZE (L.maxL)) OF L 

L : := SEQUENCE { 

m M OPTIONAL, 

iE-Extensions ProtocolExtensionContainer { {L-ExtlEs} } OPTIONAL, 

} 

L-ExtlEs RANAP-PROTOCOL-EXTENSION ::= { 

} 

ExampleMessage-Extensions RANAP-PROTOCOL-EXTENSION ::= { 



£75/ 



3GPP TS 25.41 3 version 4.1 0.0 Release 4 218 ETSI TS 1 25 41 3 V4.1 0.0 (2003-09) 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



219 



ETSI TS 125 413 V4.10.0 (2003-09) 



Annex B (informative): 
Change history 



Change history | 


TSG RAN# 


Version 


CR 


Tdoc RAN 


New 
Version 


Subject/Comment 


RAN 06 


- 


- 


RP-99746 


3.0.0 


Approved at TSG RAN #6 and placed under Change Control 


RAN 07 


3.0.0 


- 


- 


3.1.0 


Approved at TSG RAN #7 


RAN 08 


3.1.0 


- 


- 


3.2.0 


Approved at TSG RAN #8 


RAN_09 


3.2.0 


124- 
136, 
138, 
168- 
171, 
173, 
174 


RP-000373 


3.3.0 


Approved at TSG RAN #9 


RAN_09 


3.2.0 


175, 
177- 
179, 
181- 
184 


RP-000374 


3.3.0 


Approved at TSG RAN #9 


RAN_1 


3.3.0 


185- 
191, 
194- 
199, 
201, 
203- 
207, 
210- 
214, 
219, 
221- 
232, 
234, 
235 


RP-000613 
RP-000695 


3.4.0 


Approved at TSG RAN #1 


RAN_1 1 


3.4.0 


236, 
238, 
240- 
243, 
245- 
246, 
248, 
249, 
253- 
258, 
260, 
261, 
263, 
266 


RP-010110 


3.5.0 


Approved at TSG RAN #1 1 


RAN_1 1 


3.4.0 


268, 
275 


RP-010111 


3.5.0 


Approved at TSG RAN #11 





£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



220 



ETSI TS 125 413 V4.10.0 (2003-09) 



Change history 


Date 


TSG# 


TSG Doc. 


CR 


Rev 


Subject/Comment 


Old 


New 


March 01 


11 


RP-010158 


271 




Approved at TSG RAN #1 1 and placed under Change Control 


- 


4.0.0 


March 01 


11 


RP-010189 


265 




Approved at TSG RAN #1 1 and placed under Change Control 


- 


4.0.0 


March 01 


11 


RP-010156 


272, 
273, 
274 




Approved at TSG RAN #1 1 and placed under Change Control 




4.0.0 


March 01 


11 


RP-010155 


252 




Approved at TSG RAN #1 1 and placed under Change Control 




4.0.0 


March 01 


11 


RP-010163 


250 




Approved at TSG RAN #1 1 and placed under Change Control 




4.0.0 


06/2001 


12 


RP-010454 


277, 
279, 
281, 
285, 
287, 
289, 
291, 
294, 
296 
299 




Approved at TSG RAN #12 


4.0.0 


4.1.0 


06/2001 


12 


RP-010375 


301, 
315, 
317, 
319 
323 




Approved at TSG RAN #12 


4.0.0 


4.1.0 


06/2001 


12 


RP-010392 


303, 
320 




Approved at TSG RAN #12 


4.0.0 


4.1.0 


09/2001 


13 


RP-010578 


324 


1 


Correction to the Error handling of the ERROR INDICATION 
message 


4.1.0 


4.2.0 


09/2001 


13 


RP-010578 


326 


1 


Alignment of Conditional Presence with RAN3 Specification 
Principles 


4.1.0 


4.2.0 


09/2001 


13 


RP-010578 


328 




NAS Synchronisation Indicator also at RAB Establishment 


4.1.0 


4.2.0 


09/2001 


13 


RP-010578 


329 


2 


Old BSS to New BSS IE optional in UMTS to GSM handover 


4.1.0 


4.2.0 


09/2001 


13 


RP-010578 


330 




Order of elements in bitstrings 


4.1.0 


4.2.0 


09/2001 


13 


RP-010578 


337 




Data Forwarding related lEs in RELOCATION COMMAND 
message 


4.1.0 


4.2.0 


09/2001 


13 


RP-010578 


339 


1 


Error handling of the Erroneously Present Conditional les 


4.1.0 


4.2.0 


09/2001 


13 


RP-010578 


345 


1 


Rapporteurs corrections in RANAP 


4.1.0 


4.2.0 


09/2001 


13 


RP-010578 


347 


3 


Inconsistency in definition of parameters used in INVOKE_TRACE 
message 


4.1.0 


4.2.0 


09/2001 


13 


RP-010579 


359 


1 


Clarification of chapter 1 


4.1.0 


4.2.0 


09/2001 


13 


RP-010579 


364 


1 


Condition of SDU format information IE 


4.1.0 


4.2.0 


09/2001 


13 


RP-010579 


368 


1 


Relocation Requirement not to be used 


4.1.0 


4.2.0 


09/2001 


13 


RP-010594 


297 


2 


Clarification on User Plane Version Indication 


4.1.0 


4.2.0 


09/2001 


13 


RP-010594 


302 


7 


Release 4 additions in lu to support new positioning methods 


4.1.0 


4.2.0 


09/2001 


13 


RP-010698 


244 


7 


N-to-M relation between CN and UTRAN 


4.1.0 


4.2.0 


12/2001 


14 


RP-010895 


361 


3 


CR on Priority range 


4.2.0 


4.3.0 


12/2001 


14 


RP-010848 


365 




Bitstrings ordering 


4.2.0 


4.3.0 


12/2001 


14 


RP-010848 


369 


2 


UP Versions not supported 


4.2.0 


4.3.0 


12/2001 


14 


RP-010848 


371 


1 


Location Report Area 


4.2.0 


4.3.0 


12/2001 


14 


RP-010848 


378 


1 


Reason for LOCATION REPORT message is not clear 


4.2.0 


4.3.0 


12/2001 


14 


RP-010848 


380 


1 


Corrections to RRC information containers 


4.2.0 


4.3.0 


12/2001 


14 


RP-010848 


383 




Procedure Code Criticality in Error Indication 


4.2.0 


4.3.0 


12/2001 


14 


RP-010848 


386 


2 


Addition of amendment to clarify the PER encoding of bitstrings 


4.2.0 


4.3.0 


12/2001 


14 


RP-010848 


388 


2 


Chosen Integrity Protection Algorithm IE over MAP/E interface 


4.2.0 


4.3.0 


12/2001 


14 


RP-010848 


390 




Rapporteurs corrections in RANAP (MCC/MNC) 


4.2.0 


4.3.0 


12/2001 


14 


RP-010849 


394 


1 


Clarification on Location Request not fulfilled 


4.2.0 


4.3.0 


12/2001 


14 


RP-010849 


396 


1 


Subflow SDU Size clarification 


4.2.0 


4.3.0 


12/2001 


14 


RP-010849 


400 




Correction the Clause 10 Error Handling 


4.2.0 


4.3.0 


12/2001 


14 


RP-010871 


363 


1 


Cause value for not accepted relocation request 


4.2.0 


4.3.0 


12/2001 


14 


RP-010871 


367 


1 


Correction to Release 4 additions in lu to support new positioning 
methods 


4.2.0 


4.3.0 


12/2001 


14 


RP-010871 


372 




Chapter A.2.1 (EXAMPLE MESSAGE Layout) missing in version 
4.2.0 


4.2.0 


4.3.0 


12/2001 


14 


RP-010871 


373 


1 


N-to-M relation between CN and UTRAN impacts on CN initiated 
Reset Resource procedure 


4.2.0 


4.3.0 


12/2001 


14 


RP-010871 


374 




Stop Direct Report 


4.2.0 


4.3.0 


12/2001 


14 


RP-010871 


384 


1 


MCC implementation CR for corrections to Release 4 additions in 
lu to support new positioning methods. 


4.2.0 


4.3.0 


12/2001 


14 


RP-010871 


397 


1 


Correction to LCS Vertical Accurancy 


4.2.0 


4.3.0 


03/2002 


15 


RP-020164 


402 




Ouestion regarding SRNS Context Transfer and SRNS Data 
Forwarding Initiation 


4.3.0 


4.4.0 


03/2002 


15 


RP-020164 


407 




Intersystem Change and inter-system Handover corrections 


4.3.0 


4.4.0 


03/2002 


15 


RP-020164 


418 




RAB Modification Parameters 


4.3.0 


4.4.0 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



221 



ETSI TS 125 413 V4.10.0 (2003-09) 



03/2002 


15 


RP-020164 


422 


1 


Delivery of erroneous SDUs 


4.3.0 


4.4.0 


03/2002 


15 


RP-020164 


424 


2 


Handling of Global RNC-ID in Reset and Reset resource 


4.3.0 


4.4.0 


03/2002 


15 


RP-020164 


426 


2 


RABs concerned by contexts transfer 


4.3.0 


4.4.0 


03/2002 


15 


RP-020164 


432 




Alignment of definition of Guaranteed Bitrate with: 25.415 


4.3.0 


4.4.0 


03/2002 


15 


RP-020262 


435 


4 


Inclusion of "Age of Location IE into LOCATION REPORT" 


4.3.0 


4.4.0 


03/2002 


15 


RP-020179 


408 




Requirements on user plane initialisation moved to 25.415 


4.3.0 


4.4.0 


03/2002 


15 


RP-020179 


429 


1 


Correction to LCS Vertical Accuracy Code IE 


4.3.0 


4.4.0 


06/2002 


16 


RP-020401 


413 


3 


Criticality Information Decoding Failure Handling 


4.4.0 


4.5.0 


06/2002 


16 


RP-020401 


416 


4 


SDU Format Information Presence 


4.4.0 


4.5.0 


06/2002 


16 


RP-020401 


439 


2 


Erroneous Security Mode Control procedure 


4.4.0 


4.5.0 


06/2002 


16 


RP-020401 


442 




Correction of Target RNC-ID 


4.4.0 


4.5.0 


06/2002 


16 


RP-02041 7 


447 




Extension container for Last Known Service Area IE 


4.4.0 


4.5.0 


06/2002 


16 


RP-020401 


450 




"EXTENSION INDICATION" PROPOSAL 


4.4.0 


4.5.0 


06/2002 


16 


RP-02041 7 


452 




Correction of wrong implementation of CR429 


4.4.0 


4.5.0 


06/2002 


16 


RP-020401 


461 


1 


RNL-TNL coordination in RANAP 


4.4.0 


4.5.0 


06/2002 


16 


RP-020401 


464 


2 


Correction of RNC lu Coordinated relocation 


4.4.0 


4.5.0 


06/2002 


16 


RP-020401 


468 


1 


Clarification for thie usage of the cause value 


4.4.0 


4.5.0 


06/2002 


16 


RP-02041 7 


476 




Transport Layer Address at RAB modification 


4.4.0 


4.5.0 


06/2002 


16 


RP-02041 7 


478 


1 


Correction due to thie wrong implementation of CR326&244 and 
error in thie CR424 


4.4.0 


4.5.0 


09/2002 


17 


RP-020606 


480 




Erroneous criticality in DATA VOLUME REPORT REOUEST a.o. 


4.5.0 


4.6.0 


09/2002 


17 


RP-020600 


483 


2 


Handling of security at relocation 


4.5.0 


4.6.0 


09/2002 


17 


RP-020600 


494 


1 


Codec change during SRNS relocation 


4.5.0 


4.6.0 


09/2002 


17 


RP-020600 


508 


1 


Correction to RANAP cause value range 


4.5.0 


4.6.0 


09/2002 


17 


RP-020606 


511 




New cause value for RAB release request 


4.5.0 


4.6.0 


09/2002 


17 


RP-020606 


512 




LCS alignment with stage 2 


4.5.0 


4.6.0 


12/2002 


18 


RP-020751 


516 




Correction to RANAP RESET procedure 


4.6.0 


4.7.0 


12/2002 


18 


RP-020751 


521 


1 


Rel4 Common CR after RANAP review 


4.6.0 


4.7.0 


12/2002 


18 


RP-020860 


525 


4 


Correction to enable Rel4 extensions in Location Reporting Control 
procedure. 


4.6.0 


4.7.0 


12/2002 


18 


RP-020741 


528 


2 


Correction of RAB Subflows and SRBs mapping onto the transport 
channel identifiers of lur in the Source RNC to Target RNC 
transparent container 


4.6.0 


4.7.0 


12/2002 


18 


RP-020741 


531 


1 


Correction of coding of GSM lEs 


4.6.0 


4.7.0 


12/2002 


18 


RP-020751 


534 


1 


Encoding of information elements. 


4.6.0 


4.7.0 


03/2003 


19 


RP-030067 


549 




Alignment of "Uncertainty Ellipse" with RRC 


4.7.0 


4.8.0 


03/2003 


19 


RP-030056 


551 


1 


Duplicated lu connection identifiers 


4.7.0 


4.8.0 


03/2003 


19 


RP-030056 


561 




Essential correction of IMSI coding 


4.7.0 


4.8.0 


06/2003 


20 


RP-030314 


569 


2 


Essential Correction of lu Release Issue 


4.8.0 


4.9.0 


06/2003 


20 


RP-030326 


571 


1 


Correction of Failure message used for logical errors 


4.8.0 


4.9.0 


06/2003 


20 


RP-030316 


575 


2 


lu UP Initialisation during RAB modification 


4.8.0 


4.9.0 


09/2003 


21 


RP-030437 


583 


1 


Essential Correction of lu Release Request 


4.9.0 


4.10.0 



£75/ 



3GPP TS 25.413 version 4.10.0 Release 4 



222 



ETSI TS 125 413 V4.10.0 (2003-09) 



History 


Document history 


V4.0.0 


March 2001 


Publication 


V4.1.0 


June 2001 


Publication 


V4.2.0 


September 2001 


Publication 


V4.3.0 


December 2001 


Publication 


V4.4.0 


March 2002 


Publication 


V4.5.0 


June 2002 


Publication 


V4.6.0 


September 2002 


Pubhcation 


V4.7.0 


December 2002 


Publication 


V4.8.0 


March 2003 


Publication 


V4.9.0 


June 2003 


Publication 


V4.10.0 


September 2003 


Publication 



£75/